Is this knowledge article still valid?
I’ve reproduced the Postman collection locally and I’m able to successfully invoke all steps, but the acces_token value returned when calling POST /oauth/token is present, but its not a valid JWT?
Thank you for reaching out!
The usual cause for receiving an invalid JWT ( opaque token ) is that the audience parameter was not specified, or not done so correctly. You will need to pass the audience parameter in the token request, specifying the recipient, which should then return the Access Token in JWT format. Documentation for reference :
With regards to the Knowledge Article still being up to date, short answer should be yes, but to be safe, we will follow it from scratch and see if we happen to encounter any issues which might need to get addressed. If something comes up, we will update the Knowledge Article as soon as possible. Thank you for checking in with us on the matter!
Hope this helped!
Gerald
@gerald.czifra thanks for the quick reply!
Do you know if using an authorization_code grant type will influence the value associated with the audience parameter? I updated my request to pass the audience value found in our Auth0 management portal, and though I do get a token value back, it is still opaque and not a JWT.