We’re facing a problem here integrating with Apigee API Management.
As following this article:
At step to login and get the JWT token we cannot access the endpoint “authorize”. The Auth0 says:
### Oops!, something went wrong
There could be a misconfiguration in the system or a service outage. We track these errors automatically, but if the problem persists feel free to contact us.
Please try again."
I can use the “token” endpoint for example (https://latam-mplus-dev.auth0.com/oauth/token) but not the “authorize”.
I’m buinding the URL as below:
Where am I getting wrong? Any ideas?
Welcome to the Auth0 Community Forum!
Can you check your auth0 logs and see what the error is?
Let me know.
Hi @dan.woda, thanks for your reply.
In the log we have a “unknow client, failed to login” and I realized that I a made a mistake getting the wrong client_id. (I’ve taken it from API not Application)
However, I have a following doubt.
In order to integrate with Apigee, both JWT tokens are valid, right? The one that I get from oauth/token API and that other from this jwt.io screen. (after login/redirect)
Thank you very much!
I am not sure what you mean about:
The token from oauth/token endpoint should be the valid token. jwt.io is simply a debugger tool, although you could use it to create a token.
I’m sorry, I mean using that endpoint “/authorize” that shows an screen to user login and then he is redirected to jwt.io page with a JWT Token already generated.
So, thinking as a partner for example that uses “authorization grant (oauth)”, that redirect is supposed a page of him and brings him a JWT token. That is the “other” token that I was talking about.