Uploaded image for project: 'Identity'
  1. Identity
  2. ID-8790

Allow API tokens to have an "indefinite" expiry date.

XMLWordPrintable

    • 24

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Jira Software, Jira Service Management, Jira Work Management, Jira Product Discovery, Confluence

      User Problem

      With the recent changes to API tokens, all newly issued tokens are set to expire after one year. This limitation poses challenges for users who need tokens with a longer lifespan for their applications and workflows.

      Suggested Solutions

      Based on customer feedback, the current one-year expiry period does not meet the requirements of all use cases. Customers have expressed a preference for the option to set API tokens with an "indefinite" expiry date to better suit their needs.

      Current Workarounds

      Currently, there are no alternative solutions available. Customers must manually rotate their API keys prior to their expiration dates, which can be cumbersome and disruptive to their operations.

        1. image-2024-11-27-11-57-54-409.png
          image-2024-11-27-11-57-54-409.png
          173 kB

            [ID-8790] Allow API tokens to have an "indefinite" expiry date.

            Nicolas Desessart added a comment -

            We are currently considering rolling out features which will let admins extend the expiry of the tokens.

            Please provide us with a clear roadmap on when these features will be available.

            Nicolas Desessart added a comment - We are currently considering rolling out features which will let admins extend the expiry of the tokens. Please provide us with a clear roadmap on when these features will be available.

            Christopher Geelen added a comment -

            With the latest announcement ("Expiry dates will be added to existing API tokens"), it appears that the consideration of letting admins extend the expiry of tokens is not really present, but the expiry dates are further tightened.

            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.

            Christopher Geelen added a comment - With the latest announcement ("Expiry dates will be added to existing API tokens"), it appears that the consideration of letting admins extend the expiry of tokens is not really present, but the expiry dates are further tightened. 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.

            Kunwardeep Singh added a comment -

            Hi All,

            We are currently considering rolling out features which will let admins extend the expiry of the tokens.

            Kunwardeep Singh added a comment - Hi All, We are currently considering rolling out features which will let admins extend the expiry of the tokens.

              5cd8def7e384 Kunwardeep Singh
              aborzzatto Andre Borzzatto
              Votes:
              19 Vote for this issue
              Watchers:
              33 Start watching this issue

                Created:
                Updated: