Siebel Open UI, Tools, Scripting and EAI (MOSC)

MOSC Banner

Siebel Inbound WebServices using Single Sign-on

edited Dec 16, 2016 12:27AM in Siebel Open UI, Tools, Scripting and EAI (MOSC) 5 commentsAnswered
Hi,

we have a requirement where an external mobile app UI will be authenticated using Single Sign-on and want to transact with Siebel using same session details instead of providing a different user/pwd for WebService transactions.

It  seems 'EAI Object Manager' does not work if the 'sn_' cookie is set with the SSO session token unlike Application Object Manager where WebServer allows the call to Siebel Server if session token is provided.  

As per bookshelf, Single Sign-on works in Siebel Inbound WebServices using Trust Token method. So for every call to Siebel, there will be a constant Trust Token to be sent by the caller with logged in user Id. This method is not exactly a single sign-on but we are facking the concept.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center