Troubleshooting
Common issues with managed integrations and how to fix them.
Common issues and their solutions when working with managed integrations.
Agent Integrations Tab Not Visible
Symptom: You do not see the Agent Integrations tab under Settings in the Ecosystem Hub.
Cause: Agent Integrations is not enabled for your tenant. This feature must be activated by Cartesian before it becomes available.
Solution: Contact Cartesian support to enable Agent Integrations for your tenant.
Missing Signing Key (HTTP 422)
Symptom: The Agent Integrations API returns a 422 Unprocessable Entity error when your managed integration attempts to exchange an access key for a JWT token.
Cause: No signing key has been generated for your tenant. A signing key is required to sign JWT tokens.
Solution: Generate a signing key in the Ecosystem Hub under Settings > Agent Integrations. See Generating a Signing Key for step-by-step instructions.
Expired Access Key
Symptom: Authentication requests fail even though the access key was previously working.
Cause: The access key has passed its expiration date.
Solution:
- In the Ecosystem Hub, navigate to Settings > Agent Integrations.
- Check the Expires column in the access keys table for your key.
- If the key has expired, create a new access key and update your integration with the new key value.
Outpost Not Recognizing the Signing Key
Symptom: An Outpost rejects JWT tokens even though the signing key and access keys are correctly configured.
Cause: The Outpost has not been synced with the current signing key. While key distribution is normally automatic, this can occasionally happen after a key rotation or if the Outpost was provisioned before the signing key was generated.
Solution: In the Ecosystem Hub, navigate to Settings > Agent Integrations and click Reset outpost to use this key. This syncs all connected Outposts to use the current signing key. See Resetting Outposts for details.