Repository navigation
Replies: 3 comments 6 replies
|
This looks like an issue which needs to be fixed. |
|
Could you please elaborate on how your application is linked to Keycloak? Does it use the Keycloak connector, and need help with how it should be configured, or does it just use the Keycloak SSO service? As you have mentioned, the application must check various security components of the tokens (such as signatures and the audience attribute) to ensure that the data is correct, but Keycloak itself (the SSO service) cannot enforce that. |
|
Hello everyone, I recently used a "security assessment and penetration testing" tool to test Keycloak. Test was done as part of penetration testing. Details of test procedure :
Please find the attached screenshot for reference. |
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
I am currently working on an application that uses Keycloak as the Identity and Access Management (IAM) solution. I have encountered a potential security issue where the application accepts JSON Web Tokens (JWT) that are signed with the NONE algorithm.
From my understanding, if the application accepts JWTs signed with the NONE algorithm, it allows anyone to create their own "signed" tokens with arbitrary payloads. This could enable malicious users to tamper with the payload in the JWT, compromising data integrity and potentially allowing attackers to bypass authorization checks to gain arbitrary account access.
I would like to ask the community for insights and recommendations on the following points:
I appreciate any insights or recommendations you can provide on this matter.
Best regards,
Sarthak Saxena
All reactions