Using SWAM authentication will not create a WASReqURL cookie
 Technote (troubleshooting)
 
Problem(Abstract)
When WebSphere® is set to use the SWAM authentication, as opposed to LTPA, and a login is prompted, the originally requested URL is not stored in the WASReqURL cookie.
 
Cause
SWAM doesn't use the WASReqURL cookie to store the originally requested URL.
 
Resolving the problem
SWAM stores the originally requested URL in the session information, and retrieves it after authentication using the JSESSIONID value. LTPA keeps the original URL separate from the session information in its own cookie, WASReqURL.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Security
Operating system(s): z/OS
Software version: 6.1
Software edition:
Reference #: 1247905
IBM Group: Software Group
Modified date: Oct 18, 2006