Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1365

Allow SSH key management at the global/team level instead of by each user individually

XMLWordPrintable

    • 4

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

      Please add functionality to allow a global admin user to arrange SSH keys for every user that is granted access to the repositories.

      For example, as an individual user I can add my SSH keys at page: https://bitbucket.org/account/user/kallon/ssh-keys/

      But we'd like to add per-user (staff members) SSH keys through a team/group orientated admin settings page like at: https://bitbucket.org/account/user/invigorgroup/ssh-keys/

      I am disappointed that an Admin user cannot administer the keys for everyone accessing the repositories.

      For example, if we have a policy that we must reset all SSH keys every 6 months, there is no way to enforce that.
      I could remove the user from having access to the repos until they change their keys, but how would I know if they have actually changed the key?
      There could be a notification I can configure that will guarantee specific notification that a user's key has been removed and replaced with a different one.

      Cheers

            [ACCESS-1365] Allow SSH key management at the global/team level instead of by each user individually

            Alastair Wilkes added a comment -

            Bitbucket users own their own accounts. As a result, admins are not able to manage or view a user's authentication methods. The exception to this is the ability to require two factor verification, which is enforced when the user tries to access the resource. We could do something similar here - e.g. check how old a user's key is when trying to access your team's repositories - but at this time we're not seeing a lot of demand for SSH key management.

            Alastair Wilkes added a comment - Bitbucket users own their own accounts. As a result, admins are not able to manage or view a user's authentication methods. The exception to this is the ability to require two factor verification, which is enforced when the user tries to access the resource. We could do something similar here - e.g. check how old a user's key is when trying to access your team's repositories - but at this time we're not seeing a lot of demand for SSH key management.

              Unassigned Unassigned
              0505797b698e Kallon Weingarten
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: