LDAP: error code 80

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2016 01:55 AM
Hello Experts,
Need your assistance on an issue. I am trying to bind an AD LDS server with servicenow for data import and authenticating users via Single Sign On. The Mid Server is up and validated and is placed in DMZ due to some security concerns, I am unable to bind and getting below error everytime I test connection.
LDAP: error code 80 - 80090304: LdapErr: DSID-0C0903D9, comment: AcceptSecurityContext error, data 20ee, v2580
The ports are enabled too, not sure what could be the cause.
Any advice ?
Thanks and Regards,
Ayush Saxena
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2016 02:03 AM
Hi Ayush,
Is the account you are using to connect to AD with disabled, or has the password for the account expired? If you have the option, it would be worth trying another account you know is using the correct credentials.
https://support.microsoft.com/en-us/kb/919336
active directory - LDAPException when trying to connect using userPrincipalName - Stack Overflow
Regards,
Sean

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2016 02:11 AM
Hi Sean,
I checked the account is active and have password never expired set as true.
Regards,
Ayush Saxena
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2016 05:56 AM
Apologies Ayush, I'm not sure what the issue could be.
The wiki confirms that error code 80 is an unspecified error (http://wiki.servicenow.com/index.php?title=LDAP_Error_Codes#gsc.tab=0), so you should be able to rule out anything that appears on table. However, I can't help you any further than that unfortunately.
Regards,
Sean

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2016 03:11 AM
Thanks Sean for your assistance on this. I tried reaching Servicenow support on this too, even they have no clue what it could be ,
I am badly stuck here.