This is an Early AccessEarly Access (EA) features are opt-in features that you can try out in your org by asking Okta Support to enable them. Additionally, the Features page in the Okta Admin Console (Settings > Features) allows Super Admins to enable and disable some EA features themselves. feature. To enable it, please contact Okta Support.
Connecting to Okta using the LDAP Interface
The LDAP Interface allows cloud-based LDAP authentication against UD instead of an LDAP server or Active Directory (AD). Because these apps are authenticated against UD, it allows Okta to control access and centralize credentials for applications that support the LDAP authentication protocol.
The LDAP Interface is a cloud proxy that consumes LDAP commands and translates them to Okta API calls, providing a straightforward path to authenticate legacy LDAP apps in the cloud. This also enables you to centralize and manage all your LDAP resources (policies, usersIn Okta literature, we generally refer to "users" as the people who serve as Okta administrators. When we refer to "end users" we are generally referring to the people who the administrators serve. That is, those who use Okta chiclets to access their apps, but have no administrative control., apps) within Okta. You can also add seamless MFA with Okta Verify Push to your LDAP apps, providing an extra layer of security.
With typical LDAP integrations, a physical Okta LDAP agentA software agent is a lightweight program that runs as a service outside of Okta. It is typically installed behind a firewall and allows Okta to tunnel communication between an on-premises service and Okta's cloud service. Okta employs several agent types: Active Directory, LDAP, RADIUS, RSA, Active Directory Password Sync, and IWA. For example, users can install multiple Active Directory agents to ensure that the integration is robust and highly available across geographic locations. is required. The LDAP Interface allows you to connect LDAP applications to Okta's Universal Directory without installing and maintaining physical LDAP agents:
How is this different from Okta's LDAP Agent?
The LDAP agent is meant to synchronize identities to or from an existing LDAP directory. The LDAP interface, on the other hand, allows you to migrate certain apps off of unnecessary LDAP or AD servers and onto Okta.
But in certain cases, you may not be in a position to deprecate your LDAP or AD servers, in which case synchronization may be the more pragmatic solution. Additionally, unlike the LDAP interface which Okta manages in the cloud, the LDAP agent usually has to be deployed inside your firewall.
With the LDAP interface, authentication is done directly against Okta. In addition, the LDAP interface supports other LDAP functions like search.
All the authentication policies for the LDAP interface go through the Okta sign on policy. If you want to require that LDAP apps use MFA you can set up specific network zones for the LDAP apps that will be connecting to Okta and MFA policies for those zones. Then any connections coming from those LDAP apps will be required to use MFA. You can also do the reverse and use policies to prevent MFA from being required when accessing LDAP apps.
- Admins are able to configure an application that currently authenticates users against an LDAPv3 directory to authenticate against Okta's LDAP interface instead.
- Admins are also able to perform basic search functionality via LDAP SEARCH commands.
- Only READ-only commands are supported. WRITE commands are not supported.
- Okta must be the source of truth for the apps.
- Searches are limited to returning 200 users or groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups.. Simple page results control is supported. If the search to Okta contains more than or equal to 200 entries, the LDAP server returns an error code describing the need for pagination.
- Support for TLS 1.2 only.
- Unix or Linux-based PAM authentication is not supported.
- Only Okta users and groups are supported. AD Groups are not returned.
- Ability to search on memberOf results in longer search times.
- You must use an Okta user ID. If you are using samAccountName as a log in value for your apps, authentication will fail.
- Complex searches and wild cards are not supported, with the exception of cn=*.
The specific steps to connect to Okta using the LDAP protocol will vary by application. This section provides Okta-specific values you may be prompted for.
<orgThe Okta container that represents a real-world organization._subdomain>.ldap.<okta or oktapreview or okta-emea>.com
StartTLS on port 389
LDAPS on port 636.
|Base DN||[<ouAn acronym of Organizational Unit. Organizational units are Active Directory containers into which you can place users, groups, computers, and other organizational units. It is the smallest scope or unit to which you can assign Group Policy settings or delegate administrative authority.=users or groups>],<dc=orgname>, dc=oktapreview, dc=com|
|User ID/Bind DN||
Note: Must be an adminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. but can be a Read-only admin.
<password for the admin user>
Note: You must ensure the admin doesn't require MFA.
|Additional User DN||ou=Users|
|User Object class||inetOrgPerson|
|User Name Attribute||uid|
|User Password Attribute||Okta does not expose passwords.|
|Group Object Class||groupofUniqueNames|
|Group Object Filter||Complex filters and wild cards are not supported with the exception of cn=*|
|Group Members Attribute||uniqueMember|
|User Members Attribute||
Note: memberOf is not an indexed value. Using memberOf will result in significantly slower search times.
Setting up LDAP interface for JIRA on-prem
The series of screen shots below illustrate the values required for setting up Jira on-prem. Use these as a guide for other on-prem applications that may use a similar configuration.
Note: Okta does not expose passwords.