I have an application that wants to return a response back to the browser from the EAI. In this case, the response is a dynamically created XML document. WebSEAL seems to drop this response and return a 302. I want both a security session cookie from webseal and the XML response returned in the EAI response to end up at the browser, preferably with an HTTP 200 response, but maybe other response codes.
To elaborate:
- form-based authentication, posting userID, password, registered token value to trigger URL
- WebSEAL triggers and passes request to EAI
- EAI authenticates user ID and password, invokes webservice with user ID and registered token value
- web service returns XML in its response
- EAI sets authentication headers based on XML content and passes response onto WebSEAL
- WebSEAL catches authentication headers and creates security session and set cookie header for the credential
- WebSEAL responds with a 302 and removes the response body passed through the EAI from the web service
Question: Can WebSEAL be configured to pass the response untouched other than adding the credential cookie so that the requester gets the credential and the XML message body?