Security Compliance

Authentication failed: Authenticated user was not found in LDAP

SEM requires a fully defined principle name for an account in LDAP otherwise it will be unable to find and import the user into SEM for LDAP/SSO sign in. If you review the manager.log (from the console go to the Manager menu and type showlog or watchlog) you will see this error: (Mon Sep 12 09:47:21 PDT 2016) II:INFO [SsoKeytabHandler] {http-nio-8080-exec-7:113} Kerberos user: First.Last@domain.com (Mon Sep 12 09:47:21 PDT 2016) EE:ERR [SemSpringSecurityAuthManager] {http-nio-8080-exec-7:113}

First published date

10/11/2018 4:17 PM

Last published date

10/11/2018 4:17 PM

Overview

Security Event Manager (formerly Log & Event Manager) requires a fully defined principle name for an account in LDAP. Otherwise, it will be unable to find and import the user into SEM for LDAP/SSO sign in.

If you review the manager.log (from the console go to the Manager menu and type showlog or watchlog), you will see this error:

(Mon Sep 12 09:47:21 PDT 2016) II:INFO [SsoKeytabHandler] {http-nio-8080-exec-7:113} Kerberos user: First.Last@domain.com
(Mon Sep 12 09:47:21 PDT 2016) EE:ERR [SemSpringSecurityAuthManager] {http-nio-8080-exec-7:113} Authentication failed: Authenticated user was not found in ldap.
 

Screenshot of the account in Active Directory:

Product section

Security Event Manager

Cause

The principle name is not fully qualified in Active Directory and it causes the error.

Resolution

First, make sure you are running at least 6.3.1 Hotfix 2 in SEM. There are fixes related to LDAP login issues in the hotfix. If you're still having issues, try the following steps.

  1. Find the account in Active Directory.
  2. Edit the account.
  3. Click the Account Tab.
  4. From the drop-down list to the right of the User logon name, select the domain the account belongs to.
    Correctly configured account: