Troubleshoot
Fix common HackerOne integration errors
This page lists common errors and known issues encountered while integrating HackerOne with Zluri, and instructions on how to fix them.
If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].
HAC-101-A: The API key used to connect the integration is invalid. Please ensure that you use the right API key to connect the integration
The API key used to connect the integration is invalid. Please ensure that you use the right API key to connect the integration
This error occurs while connecting HackerOne to Zluri with an invalid API token. To fix this:
- Carefully follow the instructions to create a HackerOne API token.
- Copy the API token as-is while entering it in Zluri and ensure there are no missing characters.
- Verify that you're using the correct token name (aka identifier) that matches the one created in HackerOne.
Afterwards, try to connect HackerOne to Zluri again.
HAC-101-B: The API key used for this integration has expired or been revoked. Please ensure that you use the right API key before reconnecting the integration
The API key used for this integration has expired or been revoked. Please ensure that you use the right API key before reconnecting the integration
This error occurs if the API token used to connect HackerOne to Zluri has expired or been revoked.
To fix this, follow the instructions to create a HackerOne API token and reconnect the integration. Note that creating a new API token will revoke any previously generated token.
HAC-102-A: The user doesn't have sufficient permissions to connect the integration. Please ensure that the user connect has the appropriate permissions
The user doesn't have sufficient permissions to connect the integration. Please ensure that the user connect has the appropriate permissions
This error occurs when the HackerOne user does not have the necessary privileges to connect to Zluri.
To resolve this error, make sure the user creating the API token has Administrator privileges in HackerOne, and try to connect again.
HAC-102-B: The permissions of user who connected the integration have been revoked. Please reconnect the integration with a user account that has the appropriate permissions
The permissions of user who connected the integration have been revoked. Please reconnect the integration with a user account that has the appropriate permissions
This error occurs when the HackerOne user who created the API token to connect to Zluri has lost Administrator privileges.
To resolve this error, restore the user's Administrator privileges in HackerOne or use a different user with the required privileges to generate the API token and reconnect the integration.
HAC-103-A: No organizations found for the provided API key. Please ensure that the API key is associated with an active organization
No organizations found for the provided API key. Please ensure that the API key is associated with an active organization
This error occurs when the user who generated the API token is not associated with any active organization. To fix this, add the user to one or more active organizations and try to connect HackerOne to Zluri again.
HAC-103-B: The organization associated with the integration is no longer available. Please verify the organization status and reconnect
The organization associated with the integration is no longer available. Please verify the organization status and reconnect
This error occurs when the organization(s) that the user who generated the API token was a part of have been deleted or deactivated.
To fix this, add the user to one or more active organizations and try to connect HackerOne to Zluri again
Updated about 14 hours ago