Problem: Consecutive API token generation renders previous tokens invalid
Article ID: 443808
Updated On:
Products
Issue/Introduction
In the Automic REST API, generating multiple API tokens in rapid succession may cause previously generated tokens to become invalid. This issue occurs when a new token is created before the prior token is used in an API call.
Symptoms
- When creating a batch of tokens, only the most recently generated token remains functional.
- Prior tokens return authentication errors or are rendered "bad" unless an API call (such as a GET request) is performed immediately after each token's creation.
Environment
- CA Automic Workload Automation - Automation Engine
- Version 24.4.4 and lower
Cause
This is a product defect related to underlying token-handling behavior when multiple tokens are generated consecutively without intervening activity.
Resolution
Resolution:
Fixed in release 24.4.5 - not yet released.
Workaround:
To ensure all tokens remain valid in affected versions, perform a GET request using the newly created token immediately after generation and before creating the next token.
Additional Information
Users are encouraged to subscribe to this article to receive updates on the fix status. Refer to Subscribe to a Broadcom knowledge article by article or product
Feedback
