<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
0D51Y000091izU3SAIOkta Identity EngineAdvanced Server AccessAnswered2024-04-16T12:18:16.000Z2020-08-19T17:05:42.000Z2020-08-19T17:41:49.000Z

mod6f (mod6f) asked a question.

Okta LDAP interface only returns bind account

I have enabled the LDAP interface in Okta. I am able to connect to this using an LDAP bind account, I have also been able to configure this LDAP bind account to not require MFA. (This will be needed for supporting various LDAP apps.)

 

I can using the ldap bind account do an LDAP search using ldapsearch with a filter for the LDAP bind account and those details are returned. However using a filter for any account other than the bind account returns zero results. A wildcard filter e.g. uid=* only returns the LDAP bind account.

 

I even managed to get LDAP Browser working to connect to Okta and it also only returns the bind account.

 

This currently makes the LDAP interface useless. I have not yet tried it but I suspect for the same reason - whatever that is, trying to search for LDAP groups or group memberships will similarly fail.

 

What is going wrong? There are after all hardly any LDAP settings to change in Okta.

 

It is not likely to be critical, but as a related question is it possible to write via LDAP to Okta? This might be to update Department or other LDAP fields.


  • mod6f (mod6f)

    Solved it myself.

    I could not find it mentioned anywhere but the LDAP bind user needs to be at minimum a read-only Admin. If it is merely a normal account then it can only see its own record.

This question is closed.
Loading
Okta LDAP interface only returns bind account