Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Prior to account suspension, set up the notification system to send a warning notification to the user announcing that the account will be suspended. For instance, if a user has not logged in to his/her account for 90 days, the user can be notified that his their account will be suspended within the next 7 days if there continues to be no activity, after which, the account will be suspended. 

Note

Note:

  • Users who log in through the management console are not considered for account suspension since only administrative users log in through the management console. Only user accounts of users who log in using SSO or through the WSO2 IS dashboard will be suspended if idle.

Once an account is suspended, only an administrative user can unlock the account. 

Setting up account suspension notifications

...

  1. Start the WSO2 IS and log into the management console using your tenant credentials. 
  2. Click Resident under Identity Providers found in the Main tab. Expand the Login Policies tab.
  3. Expand the Account Locking tab and select the Account Lock Enabled checkbox. Click Update to save changes. 
  4. Expand the Account Management Policies tab. 

  5. Expand the Lock Idle Accounts tab and select Enable. Fill in the following fields and click Update.

    FieldDescriptionSample Value
    Lock Account AfterThis specifies the total number of days after which the account will be locked. In this case, if the account is idle for 90 days, it will be locked.90
    Alert User inThis specifies the number of days (in a comma separated list) after which the user is sent a warning notification informing him/her them that the account is about to be locked. In this case, the user will receive multiple notifications, one notification after 30 days, the next after 45 days etc. Finally if it reaches 90 days with no activity from the user, the account will be locked.30,45,60,75

Tip
titleTroubleshooting Tips

If you want to troubleshoot this feature, add the following property to the log4j.properties file found in the <IS_HOME>/repository/conf/ folder to receive DEBUG logs.

Code Block
log4j.logger.org.wso2.carbon.identity.account.suspension.notification.task=DEBUG
Panel
titleRelated Links

By default, the claim values of the identity claims used in this feature are stored in the JDBC datasource configured in the identity.xml file. See Configuring Claims for more information on how to store the claim values in the user store.