Allow traffic from the Okta AD agent to the domain controller on port 464 to resolve a provisioning failure that creates inactive Active Directory users.

The assignment of the Okta Agent Registration application to administrators is expected behavior for the Active Directory Agent OAuth 2.0 connection.

Okta Active Directory Agent version 3.18.0 and higher uses OAuth 2.0 for registration and communication, rather than an API token.

Configure Agentless Desktop Single Sign-On for multiple Active Directory domains based on the forest structure and trust relationships.

Reinstall the Windows agent or run the Linux update script to restore the Okta LDAP agent connection after a service account password change.

An incremental LDAP import captures directory changes using time stamp-based tracking to reduce import times compared to a full import.

Okta requires a full LDAP import after an import roadblock to ensure the processing of all changes from the previously failed import.

Okta AD Agent installation fails with a forest error when the installation account lacks direct membership in the target domain.

Okta generates error messages when connecting the Okta AD Agent to AWS Simple AD because the integration is unsupported.

Rejoin the server hosting the Active Directory Agent to the domain to resolve delegated authentication failures returning error code 1789.