Re: [keycloak-user] Configure Self User Registration at Client Level

+1 for the possibility to restrict users' access to specific clients. Then you would not need to implement this common usecase in every client separately. Best regards, Thomas On Apr 25, 2016 11:42 AM, "Stian Thorgersen" <sthorger(a)redhat.com&gt; wrote: This may actually we a valid use-case. Consider a setup where you have: * Two applications - one that support self-registration (let's call it public-app) the other that only admins can give access to (let's call it internal-app) * Registration enabled - default roles only give access to the public-app, but no roles for internal-app In the way it currently works the registration link is shown when user comes from either app. However, the problem is that if a user visits internal-app and clicks on register the user won't actually be able to access the application afterwards. We could add an option that hides the registration link for certain applications. In the example above if a user tries to go to "public-app" to later register for "internal-app" the user won't be able to access the app. There may even be a case for a further option that allows marking what clients a user is allowed to access. If a user tries to login to an client that the user doesn't have access to Keycloak could block the login. On 22 April 2016 at 23:15, Bill Burke <bburke(a)redhat.com&gt; wrote: _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user