GITLAB_1
Issue
Glean is unable to fetch GitLab users using the provided access token or validate that the token belongs to a GitLab administrator on a self-managed GitLab instance.
Resolution
A few possible reasons and resolutions to the issue:
Token doesn't have correct privileges or is expired
Either the token doesn't have the read_user scope, or it has expired. To resolve this:
- Follow the instructions to create a new personal access token and save it.
- Make sure to include the
read_userscope on the token.
Token doesn't belong to an admin user
The provided token doesn't have admin privileges for the self-managed GitLab instance. To resolve this:
Make sure the token belongs to a user with administrator privileges on the GitLab instance.
Glean requires read-only admin privileges to read user emails for providing access to crawled documents.
- In the setup form, make sure to unselect API token has admin privileges.
If you continue to see this error, contact Glean Support.