<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
0D54z000079iCFeCAMOkta Classic EngineDirectoriesAnswered2024-04-12T21:51:37.000Z2021-09-03T13:34:21.000Z2021-09-07T07:18:18.000Z

ts7ks (ts7ks) asked a question.

Again LDAP Provisioning Agent without uid attribute for user

 

Hi all,

we stil have the issue that the LDAP filtering of the Okta LDAP Provisioning Agent is still using uid or mail attribute for the user.

Both are not available, if we connec the Okta LDAP User Agent to an Active Directory.

This issue was described in 2019 in the support request:

LDAP Connector for AD without uid attribute (okta.com)

 

 

Does anyone know how to do a workaround?

 

 


  • Hi Harald!

     

    Whenever a custom expression is used in an AD/LDAP integration (Okta username format), Okta will use that last setting to build the query. In your case it seems it has been UID or mail in the past, or at the beginning.

    For example, with uid used the expression ends with (uid=test.user@domain.com); if email had been used in the past the query would have ended in (mail=test.user@domain.com). This can be observed if you switch to Email format and then back to your expression.

    It is possible that this is your situation as well.

     

    Also, Custom username Expressions and JIT are not compatible because of the above.

    Expand Post
This question is closed.
Loading
Again LDAP Provisioning Agent without uid attribute for user