SBL-DAT-00337: You are not able to login using the credentials returned by your security adapter.

Applies to:

Product Release: V7 (MidMarket)
Version: 7.5.3.1 [16161] MME
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-1225671801.

Symptoms

SBL-DAT-00337

We are getting ready to release our Production System and we executed the db extract and initialization process. When the initialization completed and the application was launching locally we received an error saying "You are not able to login using the credentials returned by your security adapter..... LDAPUSER (SBL-DAT-00337)".
We are able to log in through the thin client and dedicated client with ADSI configuration. Please see attached configuration files.

Solution

Message 1

For the benefit of other users:

Problem: Customer was authenticating Mobile web client with ADSI when connecting to local database. This is not supported and below is the excerpt from the Bookshelf -> Security Guide for Siebel eBusiness Applications > Security Adapter Authentication > Implementing LDAP and ADSI Security Adapter Authentication

"For a particular Siebel application, when users connect from the Siebel Dedicated Web Client to the server database, the authentication mechanism must be the same as that used for Siebel Web Client users. This mechanism could be database authentication or a supported external authentication strategy, such as LDAP or ADSI. When connecting to the local database from the Mobile Web Client, mobile users must use database authentication."

The Suggestion given to resolve the problem is as follows

To use ADSI only in the Server access, the change needed to be made would be to move the “SecurityAdapter” parameter in the .CFG file from the [Siebel] section to the [ServerDataSrc] section so the ADSI authentication would be used only in the server database access.

Customer confirmed that this worked.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.2 [16007] Fin Svcs
Database: IBM DB2/UDB 7.2
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-1083990421.

Symptoms

SBL-DAT-00170, SBL-DAT-00337

Hi,
We are trying to test the sample security adapter provided with the SDK(secsamp.cpp). We have created a shared object and copied it into the bin directory of the Siebel Server installation. We also made the necessary changes to sweapp.cfg and the Object Manager cfg file as documented in the Security Guide and the SDK README file. However it seems that when we try to test it Siebel is unable to find the dll file and we get a "Cannot load dll" error. Attached are the eapps.cfg and the uagent.cfg files. Please let us know what we are missing.

Solution

Message 1

For the benefit of other readers:

After compiling the 7.5 Sample security adapter (secsamp.cpp) the customer was unable to launch the Siebel CallCenter application. The following error message was written to the SWEAPP log file:

[966] ERROR    966: [SWSE] Set Error Response (User: Session: Error: 00028186 Message: The DLL '' libsecurityadapter.so” could not be loaded.)

This was due to error message during compilation of the security adapter. Once the compilation errors were fixed the following error message was written to the SWEAPP log file:

GenericLog    GenericLog    0    2003-09-23 13:56:01     ERROR   2314: [SWSE] Set Error Response (User: Session: Error: 00028532 Message: You are not able to login using the credentials returned by your security adapter. There may be a problem with the data source you are attempting to log into, or the credentials may be invalid for the data source. Please contact your system administrator. guestcst)

The root cause was identified as an incorrect parameter in the Security Adapter section of the configuration file. The parameters specified were

DllName                     = libsecurityadapter.so
dbUsername      = guestcst
dbUserPassword     = guestcst

(Continued on next activity)

Message 2

(Continued from previous activity)

The parameter dbUserPassword was incorrect, it should have been dbPassword. Once the parameter was change as follows the customer was able to login.

[LDAP]
DllName                     = libsecurityadapter.so
dbUsername             = guestcst
dbPassword             = guestcst

The parameters are documented in the README.txt included with "Technical Note 452: Implementing Windows integrated authentication for Siebel 7 clients"