Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Keycloak - Token inactivated after one operation #12134

Open
vunguyenhung opened this issue May 27, 2024 · 1 comment
Open

[BUG] Keycloak - Token inactivated after one operation #12134

vunguyenhung opened this issue May 27, 2024 · 1 comment
Labels
bug Something isn't working tracked internally Issue is also tracked in our internal issue tracker triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@vunguyenhung
Copy link
Collaborator

Describe the bug
Keycloak, after I connected to keycloak account, I can execute an action for example the delete user as below
image

Though after that, I couldn't fetch data anymore
image

On the source log, I see the error

2024-05-27 10:01:14 2024-05-27 03:01:14,559 DEBUG [org.keycloak.services.managers.AuthenticationManager] (executor-thread-12) Failed to verify identity token: Token is not active
2024-05-27 10:01:14 2024-05-27 03:01:14,560 DEBUG [org.keycloak.services.resources.admin.AdminRoot] (executor-thread-12) Token not valid
2024-05-27 10:01:14 2024-05-27 03:01:14,560 DEBUG [WebApplicationException] (executor-thread-12) Restarting handler chain for exception exception: jakarta.ws.rs.NotAuthorizedException: HTTP 401 Unauthorized
2024-05-27 10:01:14     at org.keycloak.services.resources.admin.AdminRoot.authenticateRealmAdminRequest(AdminRoot.java:186)
image
@vunguyenhung vunguyenhung added bug Something isn't working tracked internally Issue is also tracked in our internal issue tracker labels May 27, 2024
@dylburger dylburger added the triaged For maintainers: This issue has been triaged by a Pipedream employee label May 27, 2024
@RogerParis
Copy link

I think the reason is that the token validity of Keycloak is 1 min so it seems you need to refresh the token on the background to keep authenticated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked internally Issue is also tracked in our internal issue tracker triaged For maintainers: This issue has been triaged by a Pipedream employee
Projects
None yet
Development

No branches or pull requests

3 participants