SBL-DAT-00568: The authentication system cannot find the user with the specified username.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00568: The authentication system cannot find the user with the specified username. Please check that you have entered the username correctly or contact your system administrator for assistance.

Scope

This document is informational and intended for any user.

SBL-DAT-00568: The authentication system cannot find the user with the specified username. Please check that you have entered the username correctly or contact your system administrator for assistance.

Explanation

This is most likely that there is no user in the user repository with the specified username.

Corrective Action

Please make sure you've entered the username correctly. If you believe the user does exist and the username has been entered correctly, please check the configuration of your authentication system, that includes Siebel authentication subsystem configuration and external authentication system (such as LDAP server) configuration.

Applies to:

Siebel Tools - Version: 8.0.0.4 SIA [20417] - Release: V8

Information in this document applies to any platform.

Goal

Can we capture SBL-DAT-00568 error in the login applet and use "User Defined Errors" to replace the original OOB SBL-DAT-00568 error message?

Solution

For the benefit of other readers:

CR#12-1SB90NT "Replacing SBL-DAT-00568 error message by using script" is logged to address this Product Enhancement.

Kind Regards,

Oracle Siebel CRM Support

Applies to:

Siebel Life Sciences CRM - Version: 8.0.0.5 SIA [20420] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Customer found that they are unable to connect to the Siebel applications using Web Client after deploying a new language pack. In the Object Manager log, we found the following errors:
SecAdptLog 3rdpartyTrace 3 000000074cfc0d50:0 2010-12-06 02:38:02 (IDirectorySearch*)182d54->ExecuteSearch() with Filter '(&(objectClass=user)(uid=ANON_WEBUSER))' returns 0.
SecAdptLog 3rdpartyTrace 3 000000074cfc0d50:0 2010-12-06 02:38:04 (IDirectorySearch*)182d54->GetFirstRow(1833c0) returns 5012.
..
GenericLog GenericError 1 000000074cfc0d50:0 2010-12-06 02:38:04 (secmgr.cpp (2538) err=4597526 sys=0) SBL-SEC-10006: The authentication system cannot find the user with the specified username. Please check that you have entered the username correctly or contact your system administrator for assistance.
ObjMgrSessionLog Error 1 000000074cfc0d50:0 2010-12-06 02:38:04 (physmod.cpp (9244)) SBL-DAT-00568: The authentication system cannot find the user with the specified username. Please check that you have entered the username correctly or contact your system administrator for assistance.

Cause

During the investigation, we found that the UsernameAttributeType has been set to uid in the ADSISecAdpt

Solution

As per 'Bookshelf:Siebel Security Guide > Security Adapter Authentication > Configuring LDAP/ADSI Security Adapters'
Siebel Username Attribute: The Siebel user ID attribute used by the directory. An example entry for an LDAP directory is uid. An example entry for ADSI is sAMAccountName (maximum length 20 characters).
If your directory uses a different attribute for the Siebel user ID, enter that attribute instead. Corresponds to the UsernameAttributeType parameter.

The issue is resolved after customer change the UsernameAttributeType to sAMAccountName

Applies to:

Siebel Handheld - Version: 7.7.1 PDA [18306] to 8.1 [21039] - Release: V7 to V8

Information in this document applies to any platform.

Goal

Handheld with Store and Forward activated:

When moving from Database to LDAP authentification this requires changes in Workflow setup. Otherwise the Store and Forward functionality breaks.

Typical error message in the handheld sync object manager log file:

SBL-DAT-00568: The authentication system cannot find the user with the specified username. Please check that you have entered the username correctly or contact your system administrator for assistance

Solution

This behavior is not specific to handheld and Store and Forward messaging. This will happen to all server components which use LDAP authentification and which can be accessed in two different ways:
- directly by users
- indirectly by background components (workflow, business services, ...)

The direct access works because LDAP authentificates the user. The indirect access fails when the user under which the background component runs is not registered in LDAP.

To bypass this issue following change is suggested:
- create a new user specific for the background component
- enter this user into LDAP
- run the background component under the new user

Changes in case of Handheld with Store and Forward messaging:
- create a new user for the WfProcMgr
- enter this user into LDAP
- run the WfProcMgr component under this new user

Change Request CR 12-1REV1H5 has been raised to address this problem.