Organizations may want, or sometimes have an immediate need, to have their entire user base reset passwords. There are many ways to facilitate this within JumpCloud. There are advantages and disadvantages for each option, ways to initiate the reset flows, and variations in user experience that result.<\/p>\n\n\n\n
Expiration is a well worn method of enforcing rotation of passwords. This is typically used to manage password aging in a rotating fashion, but it may also be employed to enforce a more urgent reset across an organization\u2019s user base. This method allows some customization in how that reset is enforced and experienced by users.<\/p>\n\n\n\n
All users receive certain nudges from JumpCloud when their passwords are near expiration. These include:<\/p>\n\n\n\n
<\/p><\/div>
Linux users do not have a tray app, and will need to change their password locally on their device. If their password expires before they update their password locally, they will not be able to log in to their device. Admins will need to manually reset the user’s password from the Admin Portal.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Before enforcing any form of password expiration, there are a few settings that should be reviewed to ensure that expiration will not have undesired consequences on managed resources.<\/p>\n\n\n\n
This is a good option if there is a desire to enforce a reset, but urgency allows for this reset to take place within a prescribed timeframe. Providing a window of time for users to perform a reset can be less disruptive to productivity and distribute the potential admin remediation should a user experience confusion or challenges with the reset.<\/p>\n\n\n\n
This method of initiating reset will be far more disruptive to active users within an organization and will also ensure that compromised passwords are no longer active. Please consider the urgency of action appropriate to the identified vulnerability.<\/p>\n\n\n\n
When passwords expire, users will lose access and their account status will be updated on all JumpCloud managed resources. This may include access to emails that can notify them of expiration, communication applications commonly used to recover users, devices, and networks those devices are connected through.<\/p>\n\n\n\n
<\/p><\/div>
Linux users will be logged out of their device and require admin intervention to restore their access.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
If opting to force a reset via expiring passwords immediately, consider if you would like users to be able to self-recover from this expiration. The Allow password change after expiration<\/strong> setting, when enabled, will allow users to use their expired password to enter a reset flow in the JumpCloud User Portal or a managed device at login.<\/p>\n\n\n\n
If there isn\u2019t great urgency, requesting a reset of passwords is the least disruptive option for initiating an org-wide reset. While protecting productivity, when a request isn\u2019t disruptive, it also tends to be less effective in prompting users to take action, so this is not a recommended path of remediation if there is a concern that passwords may be compromised.<\/p>\n\n\n\n
There is a way to send a password reset request through the JumpCloud Admin Portal that comes in the form of an email to each user’s company email address. The user follows a link in the email to a reset form that requests a new password and a confirmation of that password. This is a simple flow, but as mentioned above, users may be rightfully skeptical of the request if they aren\u2019t expecting it\u2014if you decide to use this method, we suggest letting users know in advance to expect the email from JumpCloud. <\/p>\n\n\n\n
Every organization has a unique IT environment, and leverages JumpCloud to access different collections of resources. Thus, a request coming from a trusted administrator with customized instructions for a reset is likely to be more effective than a generic reset request. See\u00a0Customizing Email Templates<\/a> to learn more.<\/p>\n","protected":false},"excerpt":{"rendered":"