Jira Upgrade Steps

As part of your upgrade from Acunetix to Invicti Platform, please review your Jira integration authentication method and custom fields.

This step ensures your Issue Creator connection continues working without interruption after the upgrade.

This guide explains what's changed and what you might need to update.

1. Why You Need to Review Your Authentication Method

Invicti Platform supports fewer authentication mechanisms than Acunetix. We've deprecated some authentication types that Acunetix used, and they're no longer available in Invicti Platform.

To prevent issue creation failures, please confirm your Jira integration uses a supported authentication method.

2. What's Changed?

Authentication Options in Acunetix (Before Upgrade)

Acunetix offered four options:

• HTTP Basic Token ✔️ Supported
• HTTP Basic (Deprecated) ❌ Not supported in Invicti Platform
• Cookie (Deprecated) ❌ Not supported
• OAuth (Deprecated) ❌ Not supported

Only HTTP Basic Token remains valid going forward.

Authentication Options in Invicti Platform (After Upgrade)

Invicti Platform supports:

• Basic Authentication:
  • Jira Email + Jira API Token
• OAuth 2 (Modern) (used only in specific enterprise setups)

In most cases, you should use Basic Authentication with a Jira API token.

3. What You Need to Do

✔️ If you used "HTTP Basic Token" in Acunetix

You're already using a supported method!

Just verify that we correctly carried over these fields in Invicti Platform:

• Jira Email/Username
• Jira API Token

If everything looks correct, you don't need to take any further action.

❗ If you used any deprecated method in Acunetix

These methods won't work in Invicti Platform:

• HTTP Basic (Deprecated)
• Cookie Authentication
• OAuth (Legacy)

You'll need to switch to Basic Authentication using a Jira API Token. Learn more about setting up basic authentication.

4. How to Update Your Jira Authentication (If Needed)

Step 1: Create a Jira API Token (Atlassian Cloud)

1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
2. Click Create API Token
3. Give it a name (for example, "Invicti Integration")
4. Copy your new API token

Step 2: Configure Jira Integration in Invicti Platform

In Invicti Platform:

1. Navigate to Settings → Integrations → Issue Trackers → Jira
2. Click Edit
3. Select Basic Authentication
4. Enter:
   • Email: Your Jira email address
   • Access Token: The token you created above
5. Click Test Connection
6. Click Save

5. Verify Your Setup

After you save the updated configuration:

1. Create a quick test scan (or use an existing vulnerability)
2. Try sending an issue to Jira
3. Confirm the issue appears in the correct Jira project

If something doesn't work, our support team is here to help.

6. How We Handle Jira Fields During Upgrade

During the upgrade, Invicti Platform checks every Jira field you previously configured in Acunetix. We only carry over fields that currently exist in your Jira instance.

If a field doesn't exist in Jira (or no longer exists), Invicti Platform excludes it from the upgrade to prevent integration errors.

Why some fields might appear "missing"

If you notice a field from Acunetix isn't visible in Invicti Platform's Jira configuration, it's always because:

• The field doesn't exist in Jira (it was removed, renamed, or belongs to another project/issue type)
• The field isn't available for the specific project or issue type you've configured in the integration

Invicti Platform hides non-existent fields by design to ensure clean, valid configurations.

7. What to Do About Missing Fields

In most cases, you don't need to take any action. If you believe a field should exist:

1. Check the field's availability in Jira
2. If you recently added or modified the field, refresh the field list by editing your Jira integration settings in Invicti Platform

---

Need Help?

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