Siebel Still Creates New EAI Session Task And Logs User In With SessionToken After SessionToken Is Invalidated Earlier With SessionType=None (Doc ID 2781899.1)

Last updated on SEPTEMBER 10, 2021

Applies to:

Symptoms

When a SessionToken is sent in with SessionType=None, this will invalidate the SessionToken value, which means that Siebel will no longer accept/use the token value, so if Siebel sees this value come in, it should reject the token and return an invalid token error.

Please refer to the Siebel documentation about closing an EAI Session:

https://docs.oracle.com/cd/F26413_14/books/EAI2/web-services.html#c_Combinations_of_Session_Types_and_Authentication_Types_ahm178693

It has been observed that:

• Most times, this behaviour is working as desired: Siebel rejects the invalidated SessionToken request and returns an error message:             

This is/would be expected.

b. Or, it may open a new EAI task and process it, return a new token. This is/would not be expected.

4. The behavior may not show up immediately after each attempt, but repeat the same steps #1-3 again and it will happen. Intermittently and randomly, it'll have some occurrences where step #3 to send the invalidated token in with Stateless type does not return the error, it opens a new EAI task and runs it.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.