Repository navigation
Replies: 1 comment 3 replies
|
Keycloak is based on identity standards. Therefore, it’s common for it to be involved in the middle of the authentication process. This is why you usually request information during a step in the authentication journey or when the user is already authenticated through a required action. Once the user has the required action assigned, Keycloak executes it after the user completes the authentication process. You can also add a custom authenticator to trigger your own logic if needed. |
3 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.
In our company we originally had the T&C + accepting them implemented in our app. Now that Keycloak supports this we want to remove our implementation and rely on Keycloak. Sadly didn't find a way to link to the T&C for unregistered or registered users as the termsText seems to be locked to the login (+ required actions) flow.
I also looked for a way to create a simple page with just the
termsTextbut apparently this is not possible.I'd really like to avoid having 2 spots to maintain a legal text
All reactions