PK54749: FAILURE TO LOGIN TO WEBSPHERE APPLICATION SERVER DUE TO JSAS0130E AND JSAS0240E ERROR. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Client sometimes can not login to WebSphere Application Server via Tivoli Identity Manager due to JSAS0130E and JSAS0240E error. Following error messages are logged in SystemOut.log; <SystemOut.log> [07/08/16 18:32:45:802 JST] 111b1749 SASRas E JSAS0130E: [VaultImpl.addEstablishedCredentials] Client credentials were not valid. Restart the client so that it logs in with new credentials. Once client credentials are marked invalid, they must be thrown away and news ones created. [07/08/16 18:32:46:046 JST] 111b1749 SASRas E JSAS0240E: [CredentialsImpl.get_mapped_credentials] Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. java.lang.NullPointerException at com.ibm.ISecurityLocalObjectBaseL13Impl.CredentialsImpl. get_mapped_credentials(CredentialsImpl.java:1393) at com.ibm.ISecurityLocalObjectBasicAuthImpl.CredentialsImpl. get_mapped_credentials(CredentialsImpl.java:205)Local fix Problem summary **************************************************************** * USERS AFFECTED: Users of WebSphere Application Server * * version 5.1 * **************************************************************** * PROBLEM DESCRIPTION: Login to Tivoli Identity Manager * * fails intermittently with errors ( * * JSAS0130E and JSAS0240E ) * **************************************************************** * RECOMMENDATION: * **************************************************************** This problem occurs intermittently where the Client can not login to WebSphere Application Server 5.1.1.13 via Tivoli Identity Manager. An attempt at authenticating will fail indicating this with error messages JSAS0130E and JSAS0240E in the SystemOut.log.Problem conclusion To avoid this condition, changes include synhronization along with checking for the credential null condition before retrieving the Authentication mechanism Object ID ( OID ) . Also, additional debug trace entries were added. The fix for this APAR is currently targeted for inclusion in fixpack 5.1.1.19 Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980Temporary fix Sent the customer a test fix, waiting for feedback.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PK54749
IBM Group: Software Group
Modified date: Jun 23, 2008
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.