LI82489: PORTAL PDUR (USING LDAP) LOGIN FAILS DUE TO AN OLDER LDAP MODULE

APAR status

• Closed as program error.

Error description

• Developer Portal login fails , while using the PDUR registry
  configured with LDAP. Older version of APIC Portal has an older
  LDAP module (2.3), which fails to do a bind with an existing
  LDAP server.
  
  You should be able to see the following error in the Portal
  syslog :
  drupal: https://developer.test.com/c2%7C1643293915%7Cldap%7C172
  .x.x48%7Chttps://dev-org/xx/admin/config/people/ldap/servers/te
  st/mysite-1?render=overlay&render=overlay&render=overlay&render
  =overlay%7Chttps://developer.test.com/xx/admin/config/people/ld
  ap/servers/test/mysite-1?render=overlay&render=overlay&render=o
  verlay%7C1%7C%7CLDAPbind failure for user
  userdn=cn=apimtest,ou=AppIds,OU=MyUnit,OU=OrgTest, pass=
  drupal: https://developer.test.com/prod-int%7C1643178318%7Cldap
  _servers%7C127.0.0.1%7Chttps://developer.test.com/index.php%7C%
  7C0%7C%7CEncryptionis set to blowfish, but mcrypt module in not
  

Local fix

• N/A
  

Problem summary

• The drupal LDAP module was not compatible with the version of
  PHP in use in 5.0.8.12. That lead to errors in the UI about
  server bind failure with errors seen in the logs about mcrypt
  compatibility.
  
  This updates the module to the latest version and ensures
  compatibility with the right version of PHP.
  
  Note that this update can lead to the LDAP bind credentials
  needing to be re-entered in the portal admin UI
  (Configuration->People->LDAP).
  

Problem conclusion

• Fix targeted at 5.0.8.13
  

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 ENT

• Fixed component ID

  5725Z2201

Applicable component levels