Summary
A change was introduced in April 2025 to correct the behavior for the preserveIdleTTL parameter of the tokens/me resource. This change was rolled back in USW2 to provide affected customers with more time to update their implementation to align with the corrected behavior. Having now provided sufficient time for these customers to make the necessary corrections, we are proceeding to re-implement the change in USW2, in order to have a consistent implementation across all regions.
For additional background, refer to the Original Developer Forum Announcement. As per that announcement, we are, once again, updating the behavior in USW2 such that setting preserveIdleTTL=true will correctly leave the idle ttl of the token unmodified. Verify that any application using the tokens/me resource to prevent the token from idling is either not specifying preserveIdleTTL or explicitly setting it to false.
This announcement only relates to USW2. All other regions are unaffected as they already implemented this change in April 2025.
Effective Date
Monday, June 29, 2026
Details
The original change was reverted (in USW2 only) to provide affected customers with more time to update their implementation. However, we now have an inconsistent implementation across regions so need to reintroduce that change in USW2 to resolve that inconsistency.
Customer Impact
The current behavior of the preserveIdleTTL parameter of the tokens/me resource in USW2 was originally a product bug, which we need to correct. Some customers may have relied on this bug to achieve the desired behavior of ensuring that the user would not be logged out. These customers would send preserveIdleTTL=true, expecting that it would extend the idle ttl of the token (reset the idle ttl). Once we correct the bug (via this change), sending preserveIdleTTL=true will leave the idle ttl of the token unmodified, potentially resulting in users getting logged out earlier than expected.
Customers should review their implementation with respect to the use of the preserveIdleTTL parameter, as outlined above, and verify that any application using the tokens/me resource to prevent the token from idling is either not specifying preserveIdleTTL or explicitly setting it to false.
Impacted Resources
GET api/v2/tokens/me
Issue References
IAM-3312
SERVOPS-65025
Contacts
@David Murray Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.