Non-Expiring User Passwords in Crowd
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Some user accounts, such as service or analytics accounts, may need a non-expiring password to be set in Crowd for administration purposes. The default password age is 90 days and there is no attribute available to force the password to never expire.
Feature request: CWD-3662 - Getting issue details... STATUS
Workaround
The issue can be worked around by setting the passwordLastChanged user attribute to a date far in the future. For example, set it to 2524654861000, which is Jan 1, 2050. This will bypass the password change frequency set for the directory.
The passwordLastChanged field requires 13 digits to be entered, for example, 2535706241000 and 2535706241 both convert to May 9th, 2050, but Crowd will only recognize 2535706241000. If this field does not meet the required length, the change will save without error however the user will be prompted to reset their password on login.