From lists at merit.unu.edu Fri Aug 18 06:40:20 2017 Content-Type: multipart/mixed; boundary="===============2014705707607992691==" MIME-Version: 1.0 From: mj To: keycloak-user at lists.jboss.org Subject: [keycloak-user] default redirect url Date: Fri, 18 Aug 2017 12:40:16 +0200 Message-ID: --===============2014705707607992691== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi, Our keycloak install is on https://keycloak.company.com, proxied by = apache to localhost:8080 Some of our end-users remember that address, and browse directly to it. = So they end-up in the "welcome to keycloak" page, with links to login = the Admin Console etc. But is there a way to make the keycloak "account" client become the = default page, so that the base url would be redirected to https://keycloak.company.com/auth/realms/our_realm/account Since apache proxies the base keycloak url (localhost:8080), I guess = this would have to be done by keycloak itself. Is this possible? MJ --===============2014705707607992691==-- From john.bartko at drillinginfo.com Fri Aug 18 08:49:28 2017 Content-Type: multipart/mixed; boundary="===============8611110313165245645==" MIME-Version: 1.0 From: John Bartko To: keycloak-user at lists.jboss.org Subject: Re: [keycloak-user] default redirect url Date: Fri, 18 Aug 2017 12:49:17 +0000 Message-ID: In-Reply-To: ddb5bfed-3e73-95a7-f6ed-4bdc0f24cd34@merit.unu.edu --===============8611110313165245645== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Since requests are proxied by Apache httpd, the intermediary web server cou= ld provide redirect behavior with configuration like: RewriteEngine On RewriteCond %{REQUEST_URI} ^/$ RewriteRule ^/.*$ http://redirect-destination-host.example.com/path/to/= account/client If there is no intermediary web server to leverage, Keycloak itself can als= o satisfy this use case. To override the content rendered in response to "GET /" and "GET /auth/" re= quests, the following files can be modified: - welcome-content/index.html - themes/keycloak/welcome/index.ftl Default redirect behavior can be obtained with static HTML like the followi= ng: Hope that helps, -John Bartko ________________________________ From: keycloak-user-bounces(a)lists.jboss.org on behalf of mj Sent: Friday, August 18, 2017 5:40:16 AM To: keycloak-user Subject: [keycloak-user] default redirect url Hi, Our keycloak install is on https://keycloak.company.com, proxied by apache to localhost:8080 Some of our end-users remember that address, and browse directly to it. So they end-up in the "welcome to keycloak" page, with links to login the Admin Console etc. But is there a way to make the keycloak "account" client become the default page, so that the base url would be redirected to https://keycloak.company.com/auth/realms/our_realm/account Since apache proxies the base keycloak url (localhost:8080), I guess this would have to be done by keycloak itself. Is this possible? MJ _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user --===============8611110313165245645==-- From lists at merit.unu.edu Fri Aug 18 09:13:51 2017 Content-Type: multipart/mixed; boundary="===============2963734657868075179==" MIME-Version: 1.0 From: mj To: keycloak-user at lists.jboss.org Subject: Re: [keycloak-user] default redirect url Date: Fri, 18 Aug 2017 15:13:38 +0200 Message-ID: In-Reply-To: BL2PR18MB0769DD90BF11F8C09F39411888800@BL2PR18MB0769.namprd18.prod.outlook.com --===============2963734657868075179== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi John, On 08/18/2017 02:49 PM, John Bartko wrote: > Since requests are proxied by Apache httpd, the intermediary web server = > could provide redirect behavior with configuration like: > = > = > RewriteEngine On > RewriteCond %{REQUEST_URI} ^/$ > RewriteRule ^/.*$ = > http://redirect-destination-host.example.com/path/to/account/client Super! This works great. I chose the above apache rewrite, since that = would still work after keycloak upgrades. Also no need to remember = patching files. Great, the help was much appreciated! MJ --===============2963734657868075179==--