APAR status
Closed as program error.
Error description
When the following sequence is performed, a login exception
occurs during step 3 due to the SecurityServer object reference
still pointing to WAS server1.
1. Login to WAS server1 as user1/password1
2. Logout from WAS server1
3. Login to WAS server2 as user2/password2
4. Logout from WAS server2
5. Login to WAS server3 as user3/password3
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
* with security enabled and trying to log *
* into and out of multiple servers. *
****************************************************************
* PROBLEM DESCRIPTION: A login exception occurs during login. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An exception occurs during login when attempting to login
to a different server than originally connected to. This is
caused by a cached reference to the original server.
Problem conclusion
The code was modified by doing a new InitialContext and
lookup of the SecurityServer using a different host and port
than previously used after receiving an exception from
the old host and port. The new lookup will try to pickup the
first host and port used by the application to do the first
lookup prior to performing an authentication. Otherwise, the
default host and port of localhost:2809 is used.
See the following InfoCenter section:
Security ->
Securing Applications and their environment ->
Developing secured applications ->
Developing with JAAS to login programmatically.
Go to the bullet titled "Naming requirements for
programmatic login on a pure Java client" for more details
about security server lookup precedence.
Temporary fix Comments
APAR information |
APAR number |
PQ76786 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-07-25 |
Closed date |
2003-07-30 |
Last modified date |
2003-07-30 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|