An AD account occasionally gets locked out after intentionally logging in via Database authentication (bypassing LDAP for IT troubleshooting purposes), with the system continuing to repeatedly retry AD authentication for that account even after logging out — restarting the middleware is the only fix found so far. Is there a less disruptive alternative to a full middleware restart?

All FAQ questions / Security and access

Answer

This lockout happens at the WebLogic security realm level, due to the repeated failed AD-authentication attempts being tracked there — rather than restarting the whole middleware, use the WebLogic Admin Console directly: go to Security (under the domain root), choose Unlock User, enter the specific user ID, and save. This clears the lockout within WebLogic's own security realm without needing a full middleware restart.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Security and access questions