We have a setup of TAM-eb 6.1.1 , we are using a custom EAI application along with virtual junctions.
Issue: When user tried to access a junction resource , EAI authentication happens, user should be redirected to EAI login page but user is redircted to Webseal loginsuccess.html page with text “Your Login was successful” . It doesn’t reach the originally requested URL.
It seems like Webseal is not caching the original URL and hence the login success page is coming instead of original URL.
Please help with this issue.
Pinned topic Webseal EAI Application redirection not happening
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-05T16:35:07Z at 2013-02-05T16:35:07Z by andresmgs
firstname.lastname@example.org 060002395A33 Posts
Re: Webseal EAI Application redirection not happening2013-02-01T13:52:13ZThis is the accepted answer. This is the accepted answer.Hi Neelam,
I'm not sure whether or not the VHJ will have an influence on the behavior, but are you using the "eai-redir-url-header" for redirection?
You should be able to use this, in case WebSEAL is indeed not caching the original URL.
andresmgs 2700045C0446 Posts
Re: Webseal EAI Application redirection not happening2013-02-05T16:35:07ZThis is the accepted answer. This is the accepted answer.Hi Neel.
As Hans said before, WebSEAL uses a specific order logic to send a response after succesfull authentication via EAI. From SAM for Web 7.0's InfoCenter:
WebSEAL sends a response to the user using the following precedence: a. If automatic redirection is enabled, the user is redirected to the location specified in the WebSEAL configuration file. See WebSEAL-specified (automatic) redirection. b. If the response from the external authentication application contains the streaming flag, WebSEAL streams the original response to the client. See External authentication interface - authentication flags. c. If the initial request was cached, the request is reprocessed for the user. See Request caching with external authentication interface. d. If the response from the external authentication application contains a redirection URL header, the user is redirected to the location specified by that URL. See External authentication interface-specified redirection. e. Otherwise, WebSEAL responds with the standard login_success.html page. See Static HTML server response pages.
Check the WebSEAL administration guide related to EAI at: http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.isam.doc_70/ameb_webseal_guide/concept/con_ext_authe_intfc.html