I agree with the previous statements. Having no option for indefinite API tokens is hurting our business. Being able to refresh the expiry is an option, creating a new one / rotating is hurting us as well. 

This really impacts our environment, as also explained in https://jira.atlassian.com/browse/JSDCLOUD-14412. We currently need to use User API tokens to facilitate M2M interfacing for monitoring services with the Heartbeat API, present in Jira Service Management. However, with User API tokens getting expired, we have to manually change the API tokens on each and every service/device manually. Accessing different networks, VPNs. Doing this manually impacts our Operations significantly.

In complete agreement with Josh.

I would even suggest that the imminent update to force API expiry dates on us should be delayed until there's an actual implemented way of refreshing expiry dates programmatically or a at the very least a way to create an API token via API (we'll have to come up with our own script to update our old token storage, but that's not as bad as having to do this manually every year).

As rightly mentioned by Josh, we need the ability to Auto Rotate the API tokens. Can you pls provide any update when this will be addressed.

With today's announcement ("Expiry dates will be added to existing API tokens") this functionality has changed from a nice-to-have to a must-have for us. We need a way to programmatically rotate tokens. Otherwise, we're going to lose days of productivity every year for having to manually rotate tokens.

Any update on this FR?

Is there any update on this issue?