Thanks a lot for this great content, a question I ask to myself since I have discovered Keycloak (2=3 weeks now) is about the redirection page. Is it possible to use my own login page to directly connect a new session transparently without any redirection ?
Hi Jean-Jaurès, You can implement your own theme so that the login page will look and feel the same just like your application. See here: www.keycloak.org/docs/latest/server_development/#_themes. But you will still have the redirect. You could implement your own login logic and do the HTTP POST - but that would require additional work from you (submit, read JWT, handle errors). I guess it all depends on how much you don’t like the redirect :) I myself don’t mind it, it’s how OAuth2 from GitHub/Twitter/Facebook works and most of the users are familiar and OK with it.
@@ukaszbudnik9618 Hi what do you mean about the HTTP POST? I have a separate setup where an external application is rendering my keycloak-secured application. I want to skip the login page directly (as user is logged in on the external app) by using the keycloak token exchange where i get the user access token with the client token. However i am unable to authenticate the user. user login external app -> call keycloak api to exchange token -> use access token to authenticate user -> render keycloak-secured app
Hi Łukasz, I have watched non-stop each of your videos about KeyCloak, they are really fantastic. Thanks so much for your time and Congratulations !!!
Glad you like them!
Hi Lukasz, Unable to import the hotel_realm file. Is it because of a newer KeyCloak version?
Thanks a lot for this great content, a question I ask to myself since I have discovered Keycloak (2=3 weeks now) is about the redirection page.
Is it possible to use my own login page to directly connect a new session transparently without any redirection ?
Hi Jean-Jaurès,
You can implement your own theme so that the login page will look and feel the same just like your application. See here: www.keycloak.org/docs/latest/server_development/#_themes. But you will still have the redirect.
You could implement your own login logic and do the HTTP POST - but that would require additional work from you (submit, read JWT, handle errors).
I guess it all depends on how much you don’t like the redirect :) I myself don’t mind it, it’s how OAuth2 from GitHub/Twitter/Facebook works and most of the users are familiar and OK with it.
@@ukaszbudnik9618 Yes you are right, Clearly the theming way is a better choice ! :)
@@ukaszbudnik9618 Hi what do you mean about the HTTP POST? I have a separate setup where an external application is rendering my keycloak-secured application. I want to skip the login page directly (as user is logged in on the external app) by using the keycloak token exchange where i get the user access token with the client token. However i am unable to authenticate the user.
user login external app -> call keycloak api to exchange token -> use access token to authenticate user -> render keycloak-secured app