PI31384: ADAPTER BASED AUTHENTICATION IS BROKEN IN CASES WHERE "/INVOKE" IS NOT DEFINED AS A STATIC RESOURCE IN AUTHENTICATIONCONFIG.XML

IBM MobileFirst Platform Foundation Interim Fix README for 6.3
IBM Worklight Interim Fix README for 6.2.0.1

APAR status

• Closed as program error.

Error description

• When using adapter based authentication without defining
  "/invoke" as a static resource in authenticationConfig.xml the
  authentication fails with error 500 on the server.
  

Local fix

• It is possible to define "/invoke" as a static unprotected
  resource in authenticationConfig.xml to prevent this
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * End users using mobile apps which use adapter based          *
  * authentication                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Mobile end users will not be able to login. There will be an *
  * alert "Unexpected error..." on the mobile device.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• Adding the compression support to the /invoke endpoint caused
  this issue, we had to add additional null check to the code to
  prevent server error when the "/invoke" endpoint is not declared
  as a static resource in the authenticationConfig.xml.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WL/MFPF CONSUME

• Fixed component ID

  5725I4301

Applicable component levels

• R620 PSY

     UP

• R630 PSY

     UP