Skip to content
Snippets Groups Projects

Provide a configuration to disable `personal_access_token` generation over ssh

    • Open Issue created by Antony Saba @asaba

    Release notes

    Problem to solve

    GitLab users can create new personal access tokens using ssh. For some security conscious organizations, it may not be acceptable to provision new credentials using a fixed token such as an ssh key. This feature should be disable by administrators and group owners.

    https://docs.gitlab.com/ee/development/internal_api.html#get-new-personal-access-token

    Intended users

    User experience goal

    The instance administrators should be able to disable this feature in the admin area.

    For group using group managed accounts, they should be able to disable this for users in their group.

    Proposal

    An instance wide configuration should be added that allows an instance administrator to disable this feature.

    For instances like GitLab.com, this features should available to owners of groups using SAML/group managed accounts.

    Further details

    Permissions and Security

    Instance admins and group owners.

    Documentation

    This feature appears to not be documented, so documentation will need to be added for the the feature and the configuration available to administrators.

    Availability & Testing

    What does success look like, and how can we measure that?

    What is the type of buyer?

    Is this a cross-stage feature?

    Links / references

    Edited by Antony Saba

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply