Did you better understand the SIEBEL SSO feature ?
Do you need more help ?
Main Topics
Browse All TopicsI'm trying to configure Siebel to operate in SSO mode using OAM (formerly oblix) as the authentication prompt. Attached is the errors I am receiving. I've expanded logs and logging but still cannot get it to work. Please help.
SBL-SSM-00003: Error opening SISNAPI connection.
ProcessPluginRequest ProcessPluginRequestError 1 0000049c4ae95d1a:0 2009-11-04 13:08:10 -1508992112: [SWSE] Error in getting authenticated user for SSO.
ProcessPluginRequest ProcessPluginRequestError 1 0000049c4ae95d1a:0 2009-11-04 13:08:10 -1508992112: [SWSE] Failed to reset the query for the start command.
ProcessPluginRequest ProcessPluginRequestError 1 0000049c4ae95d1a:0 2009-11-04 13:08:10 -1508992112: [SWSE] Set Error Response (Session: Error: 10944635 Message: Web Server Authentication Failed.)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I read the manual. I understand how SSO is supposed to work. I took all the sysnapi logs up to 5. I reviewed again and again what I believe the settings to be. The error doesn't change. The expanded logs don't tell me what the issue. All I get is the message as stated. It's not very much to work with. The issue is not solved.
Regarding applications releases :
-min OAM is 10.1.4.0.1
-min SIEBEL is 7.8
Although did read that ?
http://download.oracle.com
Then what are your current parameters:
-for the URL : is the IIS virtual directory used a protected one or not ? if it's protected, how are the autorizations defined ?
-for the SWEApps cfg : can you post here the usefull part of this cfg ?
-for the SIEBEL AOM parameters : did you set those in the Gateway (siebns.dat) through admin screens or srvmgr.exe console ?
Do you have any LOG issued from the SIEBEL AOM which is the one which handles the SIEBEL session ?
Business Accounts
Answer for Membership
by: BigSchmuhPosted on 2009-11-05 at 02:31:13ID: 25748118
You have 3 authentication modes in SIEBEL:
-Database : means the Login/Pwd is send to the DBMS platform to authenticate and Connect
-SecurityAdapter (LDAP/ADSI) : means the Login/Pwd is authenticated to a LDAP compliant tree and Connact to the DBMS using some properties in the [YourSecurityAdapter] section
-Integrated SSO : means that there are NO Login/Pwd as IIS-SWE "trust" the caller and init a HTTP variable allowing to identify the employee against S_USER.LOGIN and Connect to the DBMS using some properties in the [YourSecurityAdapter] section
The Security SDK allows to create a .dll (or .so on Unix) that handles the Siebel Security API (look at the Security SDK to understand those simple API)
Logging happens at many steps:
-IIS : you may learn some info on those logs (notably if IIS is in its "Integrated Authentication" mode tio authenticate a user automatically against his Domain/ADSI)
-SWE : you may offer us some more detailed logging (see env variable to raise logging level up to 5 on the SWE server)
-AOM : if you have NO object manager LOG, this means the problem is located at the SWE