API: Preventing User Account Password Expiration for Continuous Integration

Topic

How to prevent API user account password expiration

Description

API integrations can be disrupted when user account passwords expire. This article explains how to create a dedicated API user account with a password that never expires, ensuring continuous API integration without requiring frequent password updates.

Why API passwords expire

The password expiration timer only starts after the first login to an account. Once triggered, passwords typically expire after a set period (such as 3 months), requiring updates that can disrupt API functionality.

Solution: Create a dedicated API user account

To prevent API password expiration:

  1. Create a dedicated user account specifically for API integration purposes
  2. Never log into this account directly - this prevents the password expiration timer from starting
  3. Set the password expiration policy to 'Never Expire' for this specific user

Additional recommendations

If you need to reset the password for the API user account, do so without logging into the account directly through administrative tools.

Alternative approach

If you already have an existing API user account, you can access the user's account settings and update the password expiration policy to 'Never Expire'. This will allow the API integration to continue functioning without the need to update the password periodically.

Was this article helpful?
0 out of 0 found this helpful

Article Feedback


While we can’t respond to you directly, we’d love to know how we can improve the article.

Please sign in to leave a comment.