-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add support for application/jwt
in generic OAuth handler
#1960
Comments
This is something Tolgee currently cannot handle as-is. Tolgee can only support responses in plain JSON, or fails to deserialize them. Until support is added in Tolgee itself I'm afraid there's no workaround to get this working. 😢 |
Oh, okay, I see! Thanks for having a look so quickly. I understood what the problem is and how it can be solved in my current setup - I just added a new client that does not sign the responses with RS256 so it gives back the userinfo in plain JSON https://stackoverflow.com/questions/69499368/keycloak-userinfo-not-returning-user-info-returns-what-appears-to-be-a-token Other apps in the system that use JWT tokens for communication are working with signed responses with the Firebase JWT library, so I thought maybe it can be done here in a similar manner? https://github.com/firebase/php-jwt/blob/main/src/JWT.php#L102 Or how is it better to approach this situation? It doesn't look like it's the most required feature, I know, so maybe I could prepare a PR with these changes (if I will be able to set up the project, I don't code in Java on a regular basis) |
It can be; the problem here is the deserialization step which needs to be handled when the content-type is A PR would be very appreciated! The way OAuth works currently is sub-par and I definitely want to improve it on many levels, but in the meantime these kind of changes are nice to have, and will reduce the amount of work I'll have to do later on! 😄 |
This issue is stale because it has been open for 30 days with no activity. |
application/jwt
in generic OAuth handler
Hey! I have created an issue for the SSO here: #2273 So I am closing this in favour of the master issue. |
I've set the necessary env variables to authenticate with Keycloak, the URL is formed properly, I get redirected to the Keycloak instance, authenticate there and get redirected back and then get an "Unexpected error occurred", this is what is thrown in the container logs:
Env vars that I set are:
What could be the issue here? I didn't find any similar issues on Github.
The text was updated successfully, but these errors were encountered: