Thank you Bill. If I want to restrict the access for my endpoint, for example:
- admin: can do anything: read, update, delete, create at my endpoints
- regular user: read only
Which approach would be the best with KC? Interceptors? Servlet filter?
Or there's something already implemented?
On 2014-05-27, Bill Burke wrote:
Please check out the project here. IMO, this is how you'll want
With aerogear, IMO, you'll want to remove the admin user of the master
realm. We added a feature that you can have a admin user directly in
your realm within the admin console. Please read this:
The realm import enables an admin user with permissions to modify the
On 5/27/2014 7:58 AM, Bruno Oliveira wrote:
> Good morning guys, following the requirements of Push server. We on
> AeroGear would like to restrict the scope of Admin.
> Following the integration samples here:
> The downside of remove the admin is that we can't manage our users anymore
(correct me if I'm wrong).
> This is not a big deal if you add a new user or update the current admin with the
> permissions. The odd thing is: after login I'm immediately kicked out of KC
> admin, probably I'm doing something wrong for sure, but I couldn't figure
> out yet.
> This is the piece of code being tested:
> And this is the log file:
. It seems like
> everything goes well here:
> but maybe I'm missing the mgmt configuration?
> Thanks in advance.
> keycloak-dev mailing list
JBoss, a division of Red Hat
keycloak-dev mailing list