This post is very basic troubleshooting in WebLogic Server and your starting point should be Log files . For more information on logs in WebLogic Server (Admin & Managed Server Logs) here
Issue : On login to WebLogic Console with correct credentials, you get message “username/password is not correct please try again”
Reason : User Account is locked and message on screen is misleading.
Recently my Development team contacted me with error that they can’t login to WebLogic Admin Server (/console) even with correct username/password. I tested this and faced similar issue (Your username and password are not correct please try again) .
On checking Admin Server Logs at $MW_HOME/ user_projects/ domains/ [domain_name]/ servers/ [AdminServer]/ logs/[AdminServer].log I found below entry
_______________________
####<12-Sep-2009 09:17:52 o’clock GMT> <Notice> <Security> <focusthread.com> <AdminServer> <[ACTIVE] ExecuteThread: ‘17′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<anonymous>> <> <> <1260962272097> <BEA-090078> <User weblogic in security realm myrealm has had 5 invalid login attempts, locking account for 30 minutes.>
####<12-Sep-2009 09:47:52 o’clock GMT> <Info> <Security> <focusthread.com> <AdminServer> <[ACTIVE] ExecuteThread: ‘16′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<anonymous>> <> <> <1260966764623> <BEA-090067> <User lockout expired, unlocking user weblogic in security realm myrealm.>
______________________
Account Lockout is default behaviour in WebLogic Server which locks user account for 30 minutes after 5 failed attempts (This is default policy defined in default realm “myrealm” check image below).
.
You have following options :
1) Disable lockout policy
2) Increase Lockout Threshold
3) Decrease Lockout Duration
4)User external LDAP server (iPlanet, OID, AD) to authenticate user and use password policy defined in LDAP Server
For quick fix you can disable Lockout feature in your Security Realm (avoid this in production server)
Security Realms -> Select your realm (myrealm in my case) -> User Lockout -> uncheck Lockout Enabled
.
.
More on performance troubleshooting in WebLogic Server coming soon !!!
Related Posts for Learn WebLogic with Us
- Oracle WebLogic Installation Steps
- Domain , Administration & Managed Server, Cluster in Oracle WebLogic
- Create Domain in Oracle WebLogic
- Oracle WebLogic Server - Startup/Shutdown
- Oracle WebLogic Server 10g R3 10.3 is out now
- Deploy Application on Oracle WebLogic Server
- Cluster Architecture : Oracle WebLogic Server
- Start WebLogic Server on Linux on port 80, 443 <= 1024
- JDBC (Java DataBase Connectivity ) in Oracle WebLogic - Overview
- WebLogic Server JDBC for Database connection : Step by Step
- Security in Oracle WebLogic : Realm, Security Provider, Authentication, Authorization, Users
- Deploy ADF application to Oracle WebLogic Server
- Node Manager in Oracle WebLogic Server
- Configure Oracle HTTP Server infront of Oracle WebLogic Server mod_wl_ohs
- How to install weblogic server on 64 bit O.S. (Linux /Solaris) ?
- Oracle WebLogic Login Issue : Password is not correct (Password Lock Policy)
- Oracle WebLogic Server : Node Manager in nutshell
- Certification : 1Z0-108 Oracle WebLogic Server 10g System Administrator Certified Expert
- How to integrate WebLogic with Oracle Internet Directory for Login : Authentication
- opatch, adpatch and now “smart update” (BSU) to apply weblogic patches
- Disater Recovery documentation for Oracle WebLogic Server 11g (Fusion Middleware)
- Authentication Providers in #WebLogic - Oracle Access Manager Identity Assertion for Single Sign-On and OAM Authenticator
- Error while starting WebLogic Server : java.lang.NumberFormatException: null
- #WebLogic startup prompting from username password : boot.properties
Popularity: 9% [?]




Good hands-on exercises (installation, patching, cloning), very experienced trainer worth every penny
No user commented in " Oracle WebLogic Login Issue : Password is not correct (Password Lock Policy) "
Follow-up comment rss or Leave a TrackbackLeave A Reply