Hoi,
I had the same idea initially but then I thought that simply tagging a
client as "default" would be more flexible since you have all the client
metadata, role support etc.
Cheers,
Thomas
2016-02-05 14:55 GMT+01:00 Thomas Raehalme <thomas.raehalme(a)aitiofinland.com
Hi!
How about just a default redirect URL where the user is redirected when
it's appropriate to return back to the application?
The redirection could be immediate or a link on the error view.
I think this would help avoid a lot of confusion when Keycloak for a
reason or another is not aware of the client and needs to abort the process.
Best regards,
Thomas
On Fri, Feb 5, 2016 at 3:48 PM, Thomas Darimont <
thomas.darimont(a)googlemail.com> wrote:
> Hi group,
>
> I have multiple realms and a list of clients registered within each
> realm. For each realm I'd like to configure
> a "default" client that can be used as a redirect fallback if no client
> or redirect_uri was specified in requests.
>
> The usecase is to provide some kind of "home" or "launchpad"
service
> where users are redirected to in case
> they don't know or didn't specify where to go.
> The launchpad would then present a "fancy selection" of all the apps
> (clients) that are available to the current user,
> somewhat comparable to the
https://www.google.de/intl/de/about/products/
> page.
>
> Is this already possible or considered as a feature?
>
> A default "default" client could be the account application.
>
> A quick hack I could think of would be to define a client with the name
> "default" (or another well-known name)
> and register a custom endpoint in Keycloak that would accept the
> client_id as a url parameter and redirect to the
> configured client base url.
>
> Cheers,
> Thomas
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>