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

Alternative to using user credentials for API access

    XMLWordPrintable

Details

    • 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.

    Description

      Problem Definition

      Before the implementation of Atlassian Account, users could create users with a non-valid email address for BOT accounts. After the Atlassian Account enabled, the BOT accounts are having issue as per Atlassian account - Upgrade impact.

      Since AA user can no longer create bot accounts in cloud instances. Sites that already had bot accounts are still able to continue with their old bot account but no new accounts with unverified emails can be created. Outside of that the only way to gain API access for a third party app or internal script is by using users' username and passwords which is a security concern. 

      Suggested Solution

      The best alternative to this would be for users to be able to manage API tokens that can be used with our APIs. 

      Why this is important

      • Users have many scripts run heavily for daily tasks, all these scripts are facing issues after the implementation Atlassian Account

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jbatchelor Joshua Batchelor (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: