GitLab Upgrade Steps

When upgrading from Acunetix to Invicti Platform, we automatically carry over all core GitLab integration details. However, there are important differences regarding authentication and required fields.

This document highlights what changes, what we preserve, and what you might need to review.

1. What We Carry Over

• Your existing authentication token (Personal Access Token or Impersonation Token) transfers to Invicti Platform
• Your existing GitLab project configuration carries over

2. Key Differences After the Upgrade

Authentication Token Handling

Acunetix: GitLab integration supported two authentication options:

• Personal Access Token
• Impersonation Token

Invicti Platform:

• Only Access Token authentication exists
• Whatever token you used in Acunetix—Personal Access Token or Impersonation Token—carries over as a single Access Token in Invicti Platform

note

You don't need to take further action unless the token has insufficient permissions.

Email Address Requirement

• Acunetix: The email address field wasn't mandatory
• Invicti Platform: An email address is required for GitLab integrations
• During the upgrade, Invicti Platform automatically sets the account owner's email address as the integration email

important

• We don't use the email field for authentication in GitLab integrations
• GitLab authentication continues to rely solely on the Access Token

3. Recommended Post-Upgrade Checks

1. Ensure the Access Token we carried over has the correct GitLab permissions
2. Review project and group settings, especially if you originally used Impersonation Tokens
3. Confirm the automatically assigned email address matches your organization's requirements

tip

For more information: GitLab issues

---

Need Help?

Invicti Support team is ready to provide you with technical help. Go to Help Center