Authentication Error During Authentication For User Wasadmin
Contents |
Topic: WAS ND 6.0.2.17 : Secured cluster - Can't login to admin console 4 replies Latest Post - 2009-04-03T07:02:30Z by Steven Charles Robinson Display:ConversationsBy Date 1-5 of 5 secj0118e: authentication error during authentication for user wasadmin Previous Next flames 100000MBXC 26 Posts Pinned topic WAS ND 6.0.2.17
Secj0369e: Authentication Failed When Using Ltpa.
: Secured cluster - Can't login to admin console 2009-04-01T09:07:27Z | Tags: Answered question This question
Ltpaserverobj E Secj0369e: Authentication Failed When Using Ltpa.
has been answered. Unanswered question This question has not been answered yet. All I've have WebSphere Portal cluster newly built. I configured security against ITDS. The configuration
Cwwim4537e
completed successfully, and I have to supply the correct credentials to start nodeagents and any other servers configured as part of the cell. However, I can't login to the admin console on dmgr. The dmgr server requires credentials to stop the server, and correctly takes the configured wasadmin user id and password. That same cwwim4529e user id and password returns authentication errors when trying to access the admin console. I tried entering the full dn of the wasadmin user, but no joy. I've checked server.xml and it is identical ( apart from the LDAP server name ) as a previously built UAT cluster. In System.out I can see the server connecting to the LDAP and all security initializes successfully. [31/03/09 16:56:01:916 BST] 0000000a SASRas A JSAS0001I: Security configuration initialized. [31/03/09 16:56:02:322 BST] 0000000a SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM [31/03/09 16:56:02:338 BST] 0000000a SASRas A JSAS0003I: Authentication mechanism: LTPA [31/03/09 16:56:02:338 BST] 0000000a SASRas A JSAS0004I: Principal name: ssoprdldap.tgb.acme.co.uk:389/uid=wasadmin,ou=people,o=tam,o=acme,c=gb [31/03/09 16:56:02:384 BST] 0000000a SASRas A JSAS0005I: SecurityCurrent registered. [31/03/09 16:56:12:025 BST] 0000000a LdapRegistryI A SECJ0419I: The user registry is currently connected to the LDAP server ldap: //ssoprdldap.tgb.acme.co.uk:389. But then I can't authenticate that same wasadmin user [31/03/09 17:05:14:822 BST] 00000076 FormLoginExte E SECJ0118E: Authentication error during authentication for user was
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Can't login to LDAP enabled Websphere as wasadmin Want to Advertise Here? Solved Can't login to LDAP https://www.ibm.com/developerworks/community/forums/thread.jspa?threadID=257454 enabled Websphere as wasadmin Posted on 2009-04-03 Java App Servers Application Servers 2 Verified Solutions 10 Comments 37,351 Views Last Modified: 2013-12-11 Hi, I am unable to login to Websphere any more using wasadmin. Each time I provide try to login as wasadmin I get the error "Login failed. Check the user ID and password and try https://www.experts-exchange.com/questions/24294294/Can't-login-to-LDAP-enabled-Websphere-as-wasadmin.html again." One of two things may have triggered this problem. First, the problem started after I switched wasadmin from one LDAP group to another and after a restart of the Cell/Node managers. I switched wasadmin back to the original group and restarted Websphere but I am still unable to login. Infact, when our LDAP server is monitored I don't even see a connection attempt by wasadmin. Second, I was also configuring active directory settings from within Websphere so is it possible that I have "locked myself out" of websphere. It is puzzling that websphere is not even trying to contact the LDAP server. The LDAP server is reachable via a ping from the application server. Did I somehow change a setting to tell websphere to not use LDAP? Did websphere somehow loose the LDAP host name? How can I out my settings if I can't even login to websphere? I also cannot connect via wsadmin - I get the error WASX7246E: Cannot establish "SOAP" connection to host applicationse
is a repository http://portal2portal.blogspot.com/2013/04/cwwim4529e-and-secj0369e-seen-when.html of the stuff that I learn, play with, enjoy and want to share. If you follow one of my tips, your mileage MAY well vary - Here be dragons :-) Wednesday, 10 April 2013 CWWIM4529E and SECJ0369E seen when authenticating a user in WebSphere authentication error Application Server If you see exceptions such as: -[08/04/13 13:11:01:956 BST] 0000001d LTPAServerObj E SECJ0369E: Authentication failed when using LTPA. The exception is com.ibm.websphere.wim.exception.PasswordCheckFailedException: CWWIM4529E The password verification for the 'wasadmin'principal name failed. Root cause: 'javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]; Resolved authentication error during object: 'com.sun.jndi.ldap.LdapCtx@a9d2c4f9''..[08/04/13 12:35:42:483 BST] 0000001c LTPAServerObj E SECJ0369E: Authentication failed when using LTPA. The exception is com.ibm.websphere.wim.exception.WIMException.[08/04/13 12:35:42:485 BST] 0000001c FormLoginExte E SECJ0118E: Authentication error during authentication for user wasadmin[08/04/13 12:34:41:460 BST] 0000001c UserRegistryI E SECJ0363E: Cannot create credential for the user wasadmin because of the following exception com.ibm.websphere.wim.exception.WIMException[08/04/13 12:34:41:469 BST] 0000001c LTPAServerObj E SECJ0373E: Cannot create credential for the user wasadmin due to failed validation of the LTPA token. The exception is com.ibm.websphere.wim.exception.WIMExceptionand, most tellingly: -[08/04/13 12:46:28:546 BST] 00000024 exception E com.ibm.ws.wim.adapter.file.was.FileAdapter create com.ibm.websphere.wim.exception.EntityAlreadyExistsException: CWWIM4501E An entity with same unique name, 'uid=wasadmin,o=defaultWIMFileBasedRealm', or same RDN value already exists.and ( in SystemErr.log ): -[08/04/13 12:46:28:557 BST] 00000024 SystemErr R com.ibm.websphere.wim.exc