SBL-DAT-00343: Dedicated clients are not allowed to use external authentication with this database. Contact your system administrator.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172] Fin Svcs
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.1

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

Symptoms

SBL-DAT-00343

I have been experiencing strange behavior with the thin client for our Development implementation.

I ran into this problem previously, and we thought that we narrorwed the problem down to an issue with the .srf, but I believe I was mistaken in my diagnosis.

Currently when we try to access our thin client we receive the "The Server you are accessing is unavailable......" generic error screen.

Within the SWSE logs I am receiving the following error;

     ERROR   3085: [SWSE] Set Error Response (User: Session : Error: 00027955 Message: Dedicated clients are not allowed to use external authentication with this database. Contact your system administrator. (SBL-DAT-00343))

I have reverted back to the vanilla .srf and it is not resolving the problem. We have also verified that the SiteMinder authentication is functioning as expected.

We have another environment that is using the same siebel plug-in and web server front end and it is not experiencing any problems.

Solution

Message 1

The customer currently has implemented Netegrity Siebel Connector as the Web Single Sign On solution. Periodically, in his development environment, users were not able to login to the application and the Siebel Web Extensions log file (SWSE) had the following error:

ERROR   3085: [SWSE] Set Error Response (User: Session : Error: 00027955 Message: Dedicated clients are not allowed to use external authentication with this database. Contact your system administrator. (SBL-DAT-00343))

The customer mentioned that another developer has been working on implementing the standard security adapter for LDAP authentication with a different Object Manager .

We verified that the system preference Security Adapter CRC that is discussed in Alert 769: “Unable to launch Siebel application when using LDAP/ADSI Security Adapter Authentication after a new Siebel Maintenance Release” in regards to the above error for an Siebel maintenance release installation.


This system preference contains the check sum value for the security adapter . When this preference contains a value that is not “0” or “null” , the value must match the checksum of the security adapter that is being used. In this case, the customer is using two security adapters, one from Netegrity and the standard security adapter. Each of these security adapters will have a different checksum.

Message 2

Setting the Security Adapter CRC checksum value to “0” resolved the behavior. The checksum feature for Siebel 7.5.3 is not available when two different security adapters are implemented in the same Siebel enterprise. This system preference affects all the applications using a security adapter in the enterprise.