LI80001: OAUTH AUTHENTICATION URL VALUE REFERENCING API PROPERTY IS NOT UPDATED PROPERLY DURING MIGRATION FROM V4 TO V5

microgateway-1.6.7
apiconnect-collective-member-1.5.7
apiconnect-collective-controller-linux-x86_64-2.9.2
apiconnect-collective-controller-linux-s390x-2.9.2
apiconnect-collective-controller-linux-ppc64le-2.9.2
apiconnect-collective-controller-darwin-2.9.2
apiconnect-2.7.209
APIConnect_Management_5.0.8.3_20180424-2045_a46370d60d8f_81f476a.vcrypt2
APIConnect_Management_5.0.8.3_20180424-2045_a46370d60d8f_81f476a.ova
5.0.8.3-APIConnect-Portal-Ubuntu16-20180426-2319.ova
5.0.8.3-APIConnect-Portal-Ubuntu16-20180426-2319
5.0.8.3-APIConnect-Portal-Debian7-20180426-2319
APIConnect_Management_Essentials_5.0.8.3_20180424-2045_a46370d60d8f_81f476a.vcrypt2
APIConnect_Management_Essentials_5.0.8.3_20180424-2045_a46370d60d8f_81f476a.ova
5.0.8.3-APIConnect-Portal-Essentials-Ubuntu16-20180426-2319.ova
5.0.8.3-APIConnect-Portal-Essentials-Ubuntu16-20180426-2319
5.0.8.3-APIConnect-Portal-Essentials-Debian7-20180426-2319

APAR status

• Closed as program error.

Error description

• If an API uses OAuth setting for Authentication URL to reference
  an API property, such as ${Login_URL}, in API Management v4.x,
  after upgrade to API Connect v5.x, the value remains the same,
  instead of being corrected to $(Login_URL) to match the new
  format of using parentheses instead of curly braces. As a
  result, such API that uses OAuth and password flow would fail in
  API Connect v5.x with the error message "invalid_grant" when
  trying to acquire an access token.
  

Local fix

• After migration has completed, the API can be manually updated
  to change curly braces to parentheses and then republished.
  

Problem summary

• If an API uses OAuth setting for Authentication URL to reference
  an API property, such as ${Login_URL}, in API Management v4.x,
  after upgrade to API Connect v5.x, the value remains the same,
  instead of being corrected to $(Login_URL) to match the new
  format of using parentheses instead of curly braces. As a
  result, such API that uses OAuth and password flow would fail in
  API Connect v5.x with the error message "invalid_grant" when
  trying to acquire an access token.
  

Problem conclusion

• This issue is targeted to be addressed in a future API Connect
  v5 fix pack.
  

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

  API CONNECT PRO

• Fixed component ID

  5725Z2200

Applicable component levels