Skip to main content

GitHub upgrade steps

During your upgrade from Acunetix to Invicti Platform, we carry over your GitHub integration settings automatically. However, there are a few important changes in how Invicti Platform handles authentication, project selection, and required fields.

This document explains what stays the same, what changes, and what you might need to review after the upgrade.

1. What is carried over​

  • Your existing GitHub Personal Access Token (PAT) transfers automatically
  • Your configured GitHub repository selection also carries over
  • Any repository previously integrated in Acunetix without an organization carries over in the same form (see details below)

2. Key differences after the upgrade​

Authentication Changes​

  • Invicti Platform supports only Personal Access Token (PAT) authentication
  • Acunetix previously supported HTTP Basic Auth
  • Since GitHub has deprecated HTTP Basic Auth, Invicti Platform doesn't support it—we only carry over PAT information
note

You don't need to take action unless your old configuration used Basic Auth. In that case, you'll need to generate and save a valid PAT after the upgrade.

Issue Type Field No Longer Exists​

  • Acunetix: Had an Issue Type field in the integration configuration
  • Invicti Platform: This field doesn't exist
  • During upgrade, we ignore the Issue Type setting and apply our own defaults for GitHub issue creation

Organization/Project Selection UI Changes​

Acunetix: The project dropdown listed entries as OrganizationName/ProjectName

Invicti Platform: You select Organization and Project through two separate fields:

  • Organization (dropdown)
  • Repository (dropdown)

This provides clearer and more structured configuration.

3. Repositories Without an Organization​

Some GitHub repositories don't belong to an organization (user-owned repositories).

  • We carry these repositories over to Invicti Platform without an organization selection—the integration will continue working
  • However, when you try to edit and save the integration configuration in Invicti Platform, you'll need to select an Organization per our validation rules
  • If your repository is user-owned, you might need to create or select the appropriate GitHub Organization field when saving the configuration

4. Recommended Post-Upgrade Checks​

  1. Verify your PAT is still valid
  2. Validate Organization and Project selections if you plan to modify the integration
  3. Ensure GitHub permissions associated with the PAT align with your repository's access requirements
tip

For more information: GitHub issues

Need Help?​

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

Last updated on
Was this page useful?