IT36121: TLS PROFILE CHANGES IN THE LDAP IS NOT PICKED UP BY APIC GATEWAYDIRECTOR

Fix packs for DataPower Gateway version 2018.4.1

APAR status

• Closed as program error.

Error description

• TLS Profile associated with an LDAP registry doesn't get picked
  up by the GW server correctly.
  Recreate steps :
  1. Login into
  the API Manager UI
  2. Create an OAuth Provider Resource using :
  resource owner - password grant type
  3. In the Identity
  Extraction of the OAuth, select an LDAP registry (which is
  using a TLS Client Profile) for Authentication
  4. Add the OAuth
  Provider as a security requirement for an API
  5. Republish the
  API/Product
  6. Check from the DataPower GW , for "API LDAP
  Registry" and take a note of the TLS Profile in there.
  7. Now
  go the LDAP settings in the APIM -> change the TLS Profile to
  something else -> Save
  8. Republish the API/Product
  9. Repeat
  step-6 to see if the changes got pushed into the GW
  

Local fix

• Manually change the TLS Profile from DataPower Web GUI.
  

Problem summary

• The change to LDAP is now properly reflected in the
  configuration.
  

Problem conclusion

• Fix is available in 2018.4.1.16 and 10.0.1.3
  
  
  
  For a list of the latest fix packs available, please see:
  
  https://www.ibm.com/support/pages/node/83105
  

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

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels

• R18X PSY

     UP

• RA0X PSY

     UP