Oracle Unified Directory LDAP integration reference

This topic provides reference information specific to Oracle Unified Directory (OUD) LDAP integrations. When you're installing the Okta LDAP Agent, you'll need this information to integrate your OUD directory with Okta. See Install the Okta LDAP Agent

Known issues

  • Users requesting a self password reset and who are required to change their password after it is reset by an admin, must provide their new password twice to access the Okta End-User Dashboard.
  • When the provisioning settings indicate Do nothing when users are deactivated, users remain active in Okta. When a single source provides user profile attributes, deactivated users are disconnected from the source and Okta becomes the source for user profile attributes

Integration configuration

During the initial agent install and configuration documented inInstall the Okta LDAP Agent, these are the attributes for OUD:

  • LDAP version — OUD. The OUD option is not available unless it is activated by Okta support.
  • Unique Identifier Attribute — entryuuid
  • DN Attribute — entrydn
  • User Object Class — inetorgpersonj
  • User Object Filter — (objectclass=inetorgperson)
  • *Account Disabled Attribute — ds-pwp-account-disabled
  • *Account Disabled Value — TRUE
  • *Account Enabled Value — FALSE
  • Password Attribute — userpassword
  • Password Expiration Attribute — passwordexpirationtime
  • Group Object Class — groupofuniquenames
  • Group Object Filter — (objectclass=groupofuniquenames)
  • Member Attribute — uniquemember

Schema read

To add attributes from AUX classes, add the auxiliary class as an Auxiliary Object Class to the directory provisioning configuration.

Password change

Users can change their password by selecting Settings on the Okta end user dashboard.

Password reset

Password reset is triggered by an administrator or the User Forgot Password flow.

Password reset can fail if the new password does not meet the password policy criteria.

Users cannot update expired passwords. Expired passwords must be reset by an administrator.

Password validation

Use the pwdPolicy object class to implement OUD specific password policies.

You can configure settings such as password length and expiration on your LDAP instance.

Import

There are no special considerations for OUD LDAP integrations.

JIT provisioning

There are no special considerations for OUD Just In Time (JIT) provisioning. For user identification (UID), use an email format to match the default setting for an Okta username. Do not use an external identity provider (IDP) to trigger sign in.

To make sure that JIT provisioning is successful the first time:

  • the value of the configured naming attribute (such as UID) must not exist in Okta.
  • the value of the configured naming attribute (such as UID) must be unique in all JIT-enabled directories.
  • the required attributes must present. The Okta defaults are email, givenName, sn, and uid.
  • the password must be correct.
  • the Account Disabled Attribute must be set to false on the LDAP server.

When JIT provisioning completes successfully, all of the user attributes specified on the LDAP settings page and in the Profile Editor are imported. To select additional mandatory attributes, use the Profile Editor.

Membership import

During import, if the default OUD settings are used, user groups with the objectClass groupofuniquenames are imported and added to the user specified in the uniquemember group attribute.

During import, if the membership attribute is set to seeAlso, users are assigned to the groups added to the seeAlso user attribute.

Provisioning

To allow passwords to be set when users are created or assigned, disable DelAuth, enable LDAP_PUSH_PASSWORD_UPDATES, and enable password sync on your LDAP instance. With these settings, the LDAP agent sends the PASSWORD_UPDATE action when the user logs in for the first time or when they are assigned. If you do not set these settings, the password is not transferred to your LDAP instance.

To create and assign passwords when creating user profiles:

  1. Contact Okta customer support to enable LDAP push password updates.
  2. Disable delegated authentication:
    1. In the Admin Console, go to SecurityDelegated AuthenticationLDAP.
    2. Click Edit in the Delegated Authentication pane.
    3. Clear the Enable delegated authentication to LDAP check box.
    4. Click Save.
    5. Accept the default setting to reset all LDAP user passwords and click Disable LDAP Authentication.
  3. In the Admin Console, go to DirectoryDirectory IntegrationsLDAPProvisioningTo App.
  4. Click Edit, select Enable next to Sync Password, and click Save.

    5. When Sync Password is enabled, the LDAP agent sends the action PASSWORD_UPDATE when the user signs in for the first time.

To assign existing Okta users to LDAP:

  1. In the Admin Console, go to DirectoryDirectory IntegrationsLDAPProvisioningTo App.
  2. Click Edit, select Enable next to Create Users, and click Save.
  3. Click DirectoryGroups.
  4. Select the Okta group to which you want to assign users.
  5. Click Manage Directories.
  6. Select an LDAP instance in the left pane and click Next.
  7. Enter the full distinguished name (DN) for the new user LDAP container in the Provisioning Destination DN field.
  8. Click Confirm Changes.

Troubleshooting

If LDAP directory authentication fails, the agent logs display messages similar to the following to assist with diagnosis and resolution:

Agent: Success

POST initiated with result status=SUCCESS, actionType=USER_AUTH_AND_UPDATE, actionId=ADSuk6ivp6C8SUFvs0g3, diagnostic message=, error code=, matched dn=, message=SUCCESS, result code=, vendor=OID

Agent: Delauth failure

POST initiated with result status=FAILURE, actionType=USER_AUTH_AND_UPDATE, actionId=ADSuk8MP3WZbAaI6a0g3, diagnostic message=, error code=49, matched dn=cn=multyGroup_user,ou=QA_users,dc=okta-labs,dc=com, message=LDAPException(resultCode=49 (invalid credentials), errorMessage='invalid credentials'), result code=invalid credentials, vendor=OID

Agent: No user

POST initiated with result status=FAILURE, actionType=USER_AUTH_AND_UPDATE, actionId=ADSuka2mNw4Od03nT0g3, diagnostic message=, error code=, matched dn=, message=User not found while executing query: (&(objectclass=inetorgperson)(uid=multyGroup_use2r2@oud.com)), result code=, vendor=OID

Agent: Password expired

POST initiated with result status=FAILURE, actionType=USER_AUTH_AND_UPDATE, actionId=ADSukopQ97ekiE9Vs0g3, diagnostic message=, error code=49, matched dn=cn=multyGroup_user,ou=QA_users,dc=okta-labs,dc=com, message=LDAPException(resultCode=49 (invalid credentials), errorMessage='invalid credentials', responseControls={PasswordExpiredControl(isCritical=false)}), result code=PASSWORD_EXPIRED, vendor=OID

Agent: Locked Out or Deactivated

POST initiated with result status=FAILURE, actionType=USER_AUTH_AND_UPDATE, actionId=ADSulagVTomxeCFW40g3, diagnostic message=, error code=49, matched dn=cn=multyGroup_user,ou=QA_users,dc=test,dc=com, message=LDAPException(resultCode=49 (invalid credentials), errorMessage='invalid credentials'), result code=invalid credentials, vendor=OID

Agent: User deactivated

POST initiated with result status=FAILURE, actionType=USER_AUTH_AND_UPDATE, actionId=ADSuku4YaIzfj8lcL0g3, diagnostic message=, error code=49, matched dn=cn=multyGroup_user,ou=QA_users,dc=okta-labs,dc=com, message=LDAPException(resultCode=49 (invalid credentials), errorMessage='invalid credentials'), result code=invalid credentials, vendor=OID