When configuring connectors for Okta Identity Security Posture Management (ISPM), certain third-party integrations require specific token formats and prefixes to authenticate successfully. Using an unsupported token type will result in connection failures.

• Adding a GitLab Connector
• Identity Security Posture Management (ISPM)
• Using a Token for the Connector
• Okta Classic Engine
• Okta Identity Engine (OIE)

The Okta ISPM GitLab connector requires a Personal Access Token with the glpat- prefix.

How to Generate the Correct GitLab Token:

1. Log in to the GitLab instance.

2. Navigate to the User Settings by selecting the username/avatar in the top-right corner.

3. Click on Preferences.

4. From the left-hand sidebar, go to Access > Personal access tokens.

5. Select Add new token (or Legacy Token if specifically required by the instance version).

6. Configure the Token:

   • Name: Enter a descriptive name (for example, Okta ISPM Connector).

   • Scopes: Select both read_api and read_user.

7. Click Generate Personal Access Token.

8. Copy the token immediately. It will begin with glpat-. 

9. Use this full string in the ISPM connector configuration.

Similarly, to configure the GitHub connector, navigate to the GitHub developer settings and create a Classic token; verify that the generated string begins with the ghp_ prefix before saving.

Reference

• GitLab (Self-Managed) integration