SBL-SEC-00001: An error occurred loading the Siebel authentication



Applies to:


Siebel System Software - Version 7.7.2.7 SIA [18376] and later
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.7.2.7 [18376] Life Sci

Database: Oracle 9.2.0.1



*** Checked for relevance on 29-JAN-2013 ***

Application Server OS: Microsoft Windows 2000 Server SP 4

Database Server OS: Microsoft Windows 2000 Server SP 4



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







Symptoms


Hi,

we are in the process of implementing single sign on
using custom adapter. We have a dll which gets the domain\login id and
sends the login id to authentication manager.

We have configured the following for enabling single sign on

1. made the marketing_enu virtual directory as windows integrated authentication in IIS
2. updated eapps.cfg with following parameter
[defaults]
EncryptedPassword = FALSE

[/marketing_enu]
AnonUserName = sadmin
AnonPassword = sadmin
WebUpdatePassword = support
SingleSignOn = TRUE
TrustToken = LFSToken
UserSpec = REMOTE_USER
UserSpecSource = Server
ProtectedVirtualDirectory = /marketing_enu

3. updated market.cfg with the following parameter
[InfraSecMgr]
SecAdptName = MSEDLL
SecAdptMode = CUSTOM

[MSEDLL]
SecAdptDllName        = WinIntSec
DllName            = WinIntSec
SingleSignOn        = TRUE
TrustToken            = LFSToken
DbUsername            = SADMIN
dbPassword            = SADMIN
UseAdapterUsername    = TRUE
Connectstring        = MKTOLTPD
Provider            = MSDAORA.1
Tableowner            = Siebel

4. created a named sub system "CustomSecAdpt" using Sub System Type "InfraSecAdpt_Custom"

5. updated the profile parameters for the named sub system
"CustomSecAdpt". See attached Profile Parameters.xls for list of
parameters


We are getting error stating "An error occurred
loading the Siebel authentication subsystem configuration parameters
from the configuration store. Please contact your system administrator
to check parameter CustomSecAdpt::singlesignon."

Please find attached log file for sweapp and siebsrvr

Please let us know the cause for this error so that we will be able to correct the same.



Cause


Configuration/ Setup



Solution



Message 1


For the benefit of others:

Description:

Customer is
trying to implement Single Sign On using the Custom Security Adapter.
When they trying to launch Siebel Marketing Application, which is
configured to use Customer Security Adapter, they are getting “Server
Busy....” error. The Object Manager log file shows the below error:


GenericLog    GenericError    1    0    2007-10-10
17:05:10    (secmgr.cpp (2278) err=7000001 sys=0) SBL-SEC-00001: An
error occurred loading the Siebel authentication subsystem configuration
parameters from the configuration store. Please contact your system
administrator to check parameter CustomSecAdpt::singlesignon.

Resolution/Workaround:


We have checked the Application.cfg file (market.cfg) and suggested
them to set the Single Sign On and the Trust Token parameters only in
the enterprise profile (i.e. CustomSecAdpt) where they typically belong,
and remove the below from the application configuration file.

Hence, market.cfg file has been modified as below:

[InfraSecMgr]
SecAdptName = CustomSecAdpt
SecAdptMode = CUSTOM

[MSEDLL]
DllName            = WinIntSec
DbUsername            = SADMIN
dbPassword            = SADMIN
UseAdapterUsername    = TRUE
Connectstring        = MKTOLTPD
Provider            = MSDAORA.1
Tableowner            = Siebel
[Continued]



Message 2


[Continued]
After making the above changes, the customer
restarted the Siebel server and tried opening the application again.
This time they encountered a crash, however, this is related to the
Custom Security Adapter Dll used. After they recompiled to create the
dll, the issue got resolved.

Hence, when implementing SSO using
Custom Security Adapter, as the enterprise profile is new since 7.7, we
can set the Single Sign On and the Trust Token parameters only in the
enterprise profile where they typically belong, and remove them from the
application configuration file.

Thank you,










Applies to:


Siebel System Software - Version 7.5.3.12 [16272] to 8.1.1.8 [23012] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.5.3.12 [16272]

Database: Oracle 9.2.0.6

Application Server OS: Microsoft Windows 2000 Advanced Server SP 2

Database Server OS: HP-UX 11i



***Checked for relevance on 01-Feb-2013***







Symptoms


We have just upgraded from Siebel 7.5.3.12 to Siebel 7.8. In our
previous Siebel version we had a Custom Security Adapter functional in
eService for SSO. After the upgrade to Siebel 7.8, we attempted to setup
the Custom Security Adapter with the parameters and recieve errors when
accessing eService SSO.

We have attached a copy of the SWSE log.



Cause


Configuration/ Setup



Solution


The customer has upgraded from Siebel version 7.5.3.12 to Siebel
version 7.8 and was interested in using the existing custom security
adapter from 7.5.3.12 environment for SSO in Siebel version 7.8.
Starting in Siebel version 7.7 and higher, the security adapter
parameters are now stored in a security adapter enterprise profile. The
rest of the SSO configuration including the Siebel web server
Extension(SWSE) remains basically the same as it was in the pre-7.7
versions.

The original error the customer was receiving in the SWSE log file is as follows:



ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18
07:19:39     6488: [SWSE] Failed to obtain a session ID. An error
occurred loading the Siebel authentication subsystem configuration from
the configuration store. More specifically, %1
Please contact your system administrator for assistance.


ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18
07:19:39     6488: [SWSE] Set Error Response (Session: Error: 00023179
Message: SBL-SEC-00001: An error occurred loading the Siebel
authentication subsystem configuration parameters from the configuration
store. Please contact your system administrator to check parameter
(null).)

This error indicates that the security adapter
enterprise profile was unable to load due to a missing parameter in its
configuration. The error does not indicate which parameter is missing.

The customer was asked to use How
Can You Enable Event Logging for the Siebel ADSI/LDAP/DB Security
Adapter with Siebel eBusiness Applications Release 7.7, 7.8 and 8.0?
(Doc ID 477959.1) to increase security adapter logging. This logging is done in the Object Manager log file on the Siebel server.

After increasing the log levels, the Object Manager .Log file contained the following error:

GenericLog    GenericError    1    0    2006-04-19
06:16:18    (secmgr.cpp (1398) err=7000001 sys=0) SBL-SEC-00001: An
error occurred loading the Siebel authentication subsystem configuration
parameters from the configuration store. Please contact your system
administrator to check parameter CUSTOMSecAdpt::Config Section Name.

This error indicated that the custom security adapter enterprise profile parameter Config Section Name was missing.


We then focused on the translation of the security adapter parameters
in the Siebel version 7.5 Object Manager .cfg file to the Siebel version
7.8 enterprise profile.

Here is the 7.5 section from the 7.5 Object Manager .cfg file

[FileSecurityAdapter]
DllName      = <security adapter .dll name>
FileName     = <path to an .ini file that was used by the security adapter>
SingleSignOn = TRUE
TrustToken   = <TrustToken value>
SharedCredentialsDN = dbshared

A custom security adapter enterprise profile(Sub System Type = InfraSecAdpt_Custom) was created.  

The Object Manager component parameters were set to use this profile with these parameters:
Security Adapter Mode: CUSTOM
Security Adapter Name: <The enterprise profile alias name = CustomSecAdpt in this case).

In the CustomSecAdpt profile the following parameters were set:


Security Adapter Dll Name(CustomSecAdpt_SecAdptDllName ) = <security
adapter .dll name> (Assumes that the security adapter is copied to
the Siebsrvr\bin directory on the Siebel server)
Single Sign On(CustomSecAdpt_SingleSignOn) = TRUE
Trust Token(CustomSecAdpt_TrustToken) = <TrustToken value>

This left us with the following remaining parameters from the 7.5 environment:

FileName     = <path to an .ini file that was used by the security adapter>
SharedCredentialsDN = dbshared


For parameters that are used by the custom security adapter not listed
in the profile itself, the Custom security adapter enterprise profile
provides the following required parameters:

Config File Name (ConfigFileName) = <Set to the path of a .cfg file for the additional parameters>


Config Section Name(ConfigSectionName) = < The name of the bracketed
section in this file that contains these parameters>

The customer in this case created a section in the Object manager .cfg file as follows:

[ CustomParameters]
FileName     = <path to an .ini file that was used by the security adapter>
SharedCredentialsDN = dbshared

In the enterprise profile, the following parameters were set:

Config File Name (ConfigFileName) = <Set to the path of a Object Manager .cfg file > parameters>
Config Section Name(ConfigSectionName) = CustomParameters

The Siebel server was restarted so these changes took effect and this resolved the behavior.



תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - Version: 7.5.3 [16157] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3 [16157] Database: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא