Account locking and account disabling are security features in WSO2 Identity Server (IS) that can be applied to prevent users from logging in to their account and from authenticating themselves using their WSO2 IS account. The account locking feature is used to temporarily block a user from logging in, for example, in instances where there have been many consecutive, unsuccessful login attempts. Account disabling is a more of a long term security measure, which disables the account for a significant amount of time.
- First configure WSO2 Identity Server for account locking and disabling.
- Next, you can do any or all of the following:
- Enable email sending for account locking/disabling
- Configure the user store for storing relevant claims
- See the What's Next section to find out how to lock, disable or suspend user accounts.
Configuring WSO2 Identity Server for account locking and disabling
First, do the following configurations to set up account locking and disabling in WSO2 Identity Server.
The instructions given on this page follow the recommended approach for account locking and account disabling in WSO2 Identity Server, which is to use the governance
Prior to the WSO2 IS 5.2.0 release, this was configured in a different way. If you require the steps for the old method for backward compatibility purposes, see the WSO2 IS 5.2.0 documentation.
Ensure that the "
IdentityMgtEventListener" with the
orderId=50is set to false and the "
IdentityMgtEventListener" with the
orderId=95is set to true in the
This is already configured this way by default. You can skip this step if you have not changed this configuration previously.Click to see the code block
The properties that you configure in the
<IS_HOME>/repository/conf/identity/identity-event.propertiesfile are applied at the time of WSO2 Identity Server startup.
Once you start the server, any consecutive changes that you do in the
<IS_HOME>/repository/conf/identity/identity-event.propertiesfile, will not be picked up.
Start the WSO2 IS and log into the management console using your tenant credentials.
Alternatively, you can also use the
IdentityGovernanceAdminServiceSOAP service to do this instead of using the management console UI. See Calling Admin Services for more information on how to invoke this SOAP service.
If you are using the SOAP service to configure this, you do not need to follow the steps given below this note.
- Click Resident under Identity Providers found in the Main tab.
- Expand the Login Policies tab.
Expand the Account Locking tab and select the Account Lock Enabled checkbox. Click Update to save changes.
For more information about the other fields in this form, see Account Locking by Failed Login Attempts.
- To enable account locking for other tenants, log out and repeat the steps given above from step 2 onwards.
Enable email sending for account locking/disabling
Optionally, you can configure the WSO2 IS to send an email to the user's email address when the user account is locked. To configure this, follow the steps below.
- Open the
output-event-adapters.xmlfile found in the
Configure the relevant property values for the email server under the
Tip: The email template used to send the email notification for account locking is the AccountLock template and the template used for account disabling is the AccountDisable template.
You can edit and customize the email template. For more information on how to do this, see Customizing Automated Emails.