Troubleshooting: Introspection Call Fails With "invalid_request"

Version Affected: All
 
 

Overview

Making an introspection call in SecureAuth Connect can fail with "error": "invalid_request" and a 400 status code:

Cause

The client_id and client_secret keys are case-sensitive.

Resolution:

The image below shows the error. Check the case of these keys in the request body:

1. Change client_Id to client_id.
2. Change client_Secret to client_secret.

Alternatively, send the client credentials as a Bearer Token instead of in the request body.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.