Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to reduce scope of Mattermost' access to GitLab's API? #464

Open
leaf-node opened this issue Mar 7, 2024 · 0 comments
Open

Ability to reduce scope of Mattermost' access to GitLab's API? #464

leaf-node opened this issue Mar 7, 2024 · 0 comments
Labels

Comments

@leaf-node
Copy link

Thanks for your contributions to Mattermost.

Currently, the GitLab / Mattermost bridge requires granting Mattermost full API access to GitLab. From what I understand, it's equivalent to granting someone admin access, to make requests on the behalf of users of Mattermost. This poses a security risk if a Mattermost instance is ever compromised.

My feature request would be to give administrators the option of limiting the API access level, to reduce the attack surface. Some integrations like tracking private merge requests, or other privileged tasks would not be offered to users of that instance.

The level of integration could involve setting access to "read_api" for read-only access, or removing features other than the ability to log in via GitLab and interact with public repositories.

Thanks for your consideration. : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants