Troubleshooting licensing errors

Licensing issues can arise during the provisioning or setup of a Connect implementation, but they should be simple to diagnose.

403 response (feature not licensed)

When a request is denied due to licensing, it will be returned as a 403 response with a brief description describing the particular license.

{
    "status": 403,
    "title": "There is no license for requested action",
    "detail": "License for product [Vista.Connect] and feature [Vista.Subscriptions] does not exist for circuit's org code and provided jwt",
}

To resolve this issue, gather the following information:

• Feature and product information from the error message above.
• Organisation code configured for Connect.
• GAS user identifier of the request. This can be obtained from sub property of authorization JWT using a tool such as https://jwt.io/.
• Additional licensing validation information found in the Connect application logs.
• License provisioning for the GAS user in the Vista licensing system.

500 response (invalid licensing configuration)

Licensed endpoints will return a 500 if Connect isn't configured correctly to validate licenses. This is typically due to an invalid or missing configuration of the Vista Organisation Code. The Connect application logs will provide more details in this scenario.