SCM Connection - Authorization error on connect

Symptoms

• Connecting an SCM in Mobb fails with an authorization or authentication error.

• Mobb can't list or access your repositories.

Likely cause

The access token Mobb is using has expired, was revoked, or is missing the required scopes/permissions.

Resolution

1. Regenerate the access token in your SCM with the correct scopes. For example, a GitLab token needs the api and read_user scopes; a GitLab Project Access Token needs the api scope and a Developer (or higher) role.

2. Update the token in Mobb from the Integrations page (select your SCM and reconnect).

3. Confirm the token has not expired and that the account it belongs to can access the repositories you expect.

For on-premises SCMs connected through the broker, follow the platform-specific guide in Update Broker Token.

Still stuck? Contact [e-mail].