We noticed that we are getting a "OOPS An unexpected error has occured at null login.errorSessionInvalidMessage" error message on the login page after adding and activating an AD Authentication server to LDAP Authentication.
Upon troubleshooting, we noticed that when we click "Activate" on the AD server in "Manage LDAP Authentication", the auth_ldap_server is automatically deactivated.
When we inspected the ou=configuration entry in the ldap server, it shows that the default ldap server, auth_ldap_server has been disabled and the oxAuthenticationMode and oxTrustAuthenticationMode are still the default entry "simple_password_auth".
In the "Default Authentication Method" tab, the Default acr and oxTrust acr are both still the new authenticator even when the ou=configuration is still showing the default entry. Once we click update in "Default Authentication Method", the AuthenticationMode are updated and we are able to access the login page.
I have attached the ldif of ou=configuration from before adding the AD server, after adding the AD server and after updating the Default Authentication Method.
Is this the correct behaviour for adding LDAP servers?