Jive Support

Articles in this section

Back

Why Was a User's Account Automatically Disabled/Deactivated?

Author: Central KB

Overview

Jive has a built-in feature called the User Decay Task that runs automatically every day and disables non-active user accounts. If you are seeing users who have not logged in for some time having their accounts mysteriously deactivated, then this may be evidence of this feature in action.

Please note:
  • Admin user accounts will not be affected by this task.
  • User accounts that have never had a successful login attempt will not be affected by this task.
  • Jive Cloud customers will have to file a Jive Support ticket to disable or modify the settings of the User Decay Task.

Information

The default behavior of the User Decay Task is as follows:

  1. Every day, at 1:00 AM UTC, the User Decay Task executes.  Each user account's last logged-in date value is compared to the current date/time.
  2. If the difference is greater than 12 months (standard accounts), or 2 months (external contributors), then the user account is deactivated.  All content created by the user is maintained.

 

 How to check when a user was last logged in

  1. To find the Last Logged In date for a recently disabled user, log in to your Jive community site, then navigate to Your Avatar > Admin Console

    avatar-admin-console.png
     

  2. Click People, then search for the specific user.

    people-search.png
     

  3. Check the search results for the date of the user account's Last Login date, or the Last Sign in date for Hosted and On-Premise customers:

    mceclip0.png
     

  4. If the user account's last logged-in date was more than 12 months ago, then you are likely seeing the effects of the User Decay Task.

  

How to reactivate a deactivated user

  1. With the user profile open, click the Activate link 

    reactivate-user.png
     

  2. Click the Ok button on pop-up dialogue box.

    reactivate-user-ok.png
     

 

How to disable the User Decay Task

  1. The user decay task can be disabled via two system properties.  To alter them, navigate to Your Avatar > Admin Console > System > (Management) > System Properties

    system-properties.png
     

  2. To disable one or both of the tasks, set the following system properties (if they are not already listed, add them as new properties): 
    user.decay.task.enabled = false
    external.user.decay.task.enabled = false

  3. In Jive 7 and newer, this property takes effect immediately and can be confirmed by looking for the "userDecayTask" on the System Tasks Management page located at Admin console > System >
    Management > System Tasks.

 

How to reduce or extend the time before the User Decay Task deactivates a user account

Note: The default cut-off time period for deactivating standard user accounts is 12 months and for external users, it is 2 months. Standard user accounts are deactivated after 12 months of inactivity even if the system properties for the User Decay Task are not set for the instance.
  1. To extend or reduce the last-logged-in cutoff associated with the User Decay Task, set or alter the following system property, like so:

    For standard users

    user.decay.task.enabled = true
    user.decay.period = 16

    For external users

    external.user.decay.task.enabled = true
    spring.externalUserDecayRunnable.decayPeriodMonths = 16

  2. Using the above as an example, only the user accounts with the most recent login time before 16 months ago will be disabled.

  3. The task will not disable any users if the property is set to 0.

  4. A restart is required for these properties to take effect prior to Jive 7.

 

How to change when and how often the User Decay Task executes

  • The default execution time for the User Decay Task as at 1 AM UTC daily

  • To modify when this process kicks off, add or edit the system property of user.decay.task.cron.expression to change it for standard users and external.user.decay.task.cron.expression for external users, and give it a new cron expression.

For example, if you would prefer to execute the decay task only once a week, rather than nightly for a standard user, you could set this system property:

user.decay.task.cron.expressionn = 0 0 1 ? * SUN

This sets the process to occur every Sunday at 1 AM.  For more examples, see the Quartz Scheduler crontrigger documentation.

For Jive versions older than 9.6.0:

The properties names are spring.userDecayTask.cronExpression for Standard users and spring.externaluserDecayTask.cronExpression for external users. When any of these cron expressions are changed, you need to remove and add the user.decay.task.enabled property by following the below steps:

  1. Login to your Jive Admin Console.
  2. Go to System > Management > System Properties.
  3. Using the browser's search functionality (Ctrl + F), search for user.decay.task.enabled.
  4. Click the  (cross/delete) icon besides this property.
  5. You will get a notification/pop-up asking Are you sure you want to delete this property?. Click OK. This will delete the user.decay.task.enabled property.
  6. In order to add the property back, on the same page , enter:
    • user.decay.task.enabled  in the Property Name field.
    • true in the Property Value field.
  7. Click Save Property.

In order to confirm that the timing of the User Decay task is now updated, go to System > Management > System Tasks > Periodic Tasks.
Using the browser's search functionality (Ctrl + F), search for userDecayTask. It will show the updated time in the Next Execution column.

When you plan to update to Jive version 9.6.0 or later, before the deployment of the new version:

  1. Check Admin Console System Properties for presence of the deprecated property spring.userDecayTask.cronExpression.
  2. Note down its value.
  3. Remove the property.
  4. Then add property user.decay.task.cron.expression with value noted in prior step (Additional note: this final step of adding new property with noted value can be performed both before or after deployment).
Was this article helpful?
1 out of 1 found this helpful

Related articles

Comments

0 comments

Article is closed for comments.

Still Have Questions?

Our customer care team is here for you!

Submit a request