Repository navigation
Replies: 2 comments
|
@ale0hub did you find the solution for this ? |
0 replies
|
@ale0hub @Neha-Saxena15 solution is here Short summary: in my case I have got access token on host-machine's |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I have a docker container running Keycloak with a mapped external port on my computer.
I manage to request tokens to the external port from a public client (in local network) using authorization code flow.
Afterwards, I introspect a token to the external port and I get its details and whether it is active or not.
Unfortunately, if I introspect it to the internal port of the docker container I always get {active:false} even if the token has expired or not.
I am suspecting that the token must be issued from the same host (or client) where I am inspecting it but as I understand that should not matter since authorization is successfull (I receive 200 OK) and I am in "talking" to the same realm.
The introspect call to the external port or to the internal port is done in the same way, by basic Authorization for a confidential client.
I want to clarify that for both calls I am using the same realm, but different client and different host.
How can I be sure of what is missing? And what can I do to overcome that?
Thanks everyone in advance
All reactions