<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00008pcMBkSAMOkta Classic EngineLifecycle ManagementAnswered2021-12-21T23:15:36.000Z2020-06-29T17:37:46.000Z2020-07-08T13:10:02.000Z

JasonW.77028 (Customer) asked a question.

How to use 'cn' as the LDAP JIT directory integration query instead of 'uid'

Hi,

 

I am currently trying to setup our Delegated Auth using Okta and LDAP. The agent is all setup and running and the validation passed. However, our situation is a bit unique as our user's actual login value in LDAP is in the 'cn' field and not the 'uid'.

 

I am curious if there is a way to setup the agent so that it will query against 'cn' instead of (or in addition to) 'uid'.

 

Here is an example of the failure message I get when trying to do DelAuth JIT:

FAILURE: User not found while executing query: (&(objectclass=user)(uid=testUserId))

 

I would rather the query looked something like this: (&(objectclass=user)(cn=testUser))


  • sandeepk.84743 (Wipro Technologies)

    In the directory configuration specify the user attribute as CN instead of the UID. That should work fine.

    • JasonW.77028 (Customer)

      What field are you referencing? This is for an LDAP configuration.

       

      Here is my current integration configuration:

      oktaconfig

  • sandeepk.84743 (Wipro Technologies)

    In the Unique Identifier attribute specify the CN instead of distinguishname & do the validation again.

This question is closed.
Loading
How to use 'cn' as the LDAP JIT directory integration query instead of 'uid'