2014-04-22 06:48 AM
Trying to use AD authentication in OCUM 6.1 with no success:
Unable to communicate with the authentication server because the authentication server is not configured properly. Verify your authentication server configuration.
How AD should be configured to allow OCUM authenticate?
2014-05-06 12:41 PM
We are having the same issues. Have been working with our AD team and have not come up with a solution. Would like to know if this is a bug as this type of integration is usually fairly simple to setup.
2014-05-06 12:57 PM
Suggest the Active Directory Bind Account be a user that can authenticate only (Bind) to AD, not a domain admin or other user with elevated privileges.
Administrator Name can be one of three forms listed below.
Authentication Service: Active Directory
Administrator Name: <domain>\<bind_account> --or-- <bind_account>@<domain> --or-- <bind_account_distinguishedname>
Base Distinguished Name: DC=<domain>,DC=<domain>,DC=<company>,DC=<com>
At least one AD server must be entered here. IP Address or FQDN
User Name: <user_name>
The above tests should pass with a user_name of an AD account.
2014-05-06 02:10 PM
We have it setup just like the instructions call for and have tried different combinations of the instructions as well.
I just tried it with a non admin account as well and we get the same error:
"Unable to communicate with the authentication server because the authentication server is not configured properly. Verify your authentication server configuration."
2014-05-06 02:33 PM
Try disabling the nested groups user search.
Step 1: Start at the "Enable Remote Authentication" screen.
Step 2: Enable the advanced settings by selecting the "Others" authentication service name and fill in the bind and base names and password.
Step 3: Note the text in the Member text box ( member:1.2.840.1135126.96.36.1991: ).
Step 4: Edit that field so that the member line has only the text "member".
Step 5: Click save and perform a test authentication.