IAAM - LDAP Integration failing in kubernaties due to pagination

book

Article ID: 210476

calendar_today

Updated On:

Products

CA Application Test

Issue/Introduction

  Currently we are trying to integrate LDAP in the User Federation module. We added LDAP configuration correctly and test connection works fine. When we try to sync user groups getting an error.

But after trying out all possible combinations , still the integration is stuck with below error :

 javax.naming.OperationNotSupportedException: [LDAP: error code 12 - Unavailable Critical Extension]; remaining name 'cn=groups,dc=donain,dc=com'

On investigating with internal LDAP team , our LDAP servers do not support pagination but LISA is creating LDAP config with [pagination=true] by default.

Need help in taking this further.

Environment

Release : 10.5.1

Component : CA Service Virtualization

Resolution

  By default IAM uses Embeded database. Which will store details in <IAM_HOME>/standalone/data folder. We need to stop the IAM pod before connecting to this database. So, point this path in iam pod to external using persistant vols so that you can connect to the database from external server.

     Use any DB connectivity tool say DBvisualizer and configure like below to connect to the iam database. Make sure you are able to connect to database server from where you are using DB connectivity tool.

   Once the connection is established, run below query to change pagination value.

UPDATE COMPONENT_CONFIG SET VALUE=false WHERE NAME='pagination'; COMMIT;