On 2014-05-27, Bill Burke wrote:
You can use RoleAllowed on JAX-RS methods, but you'll need to
resteasy config for that. If that's what you mean. You can also use
Nailed it Bill, that's exactly what I mean.
web.xml servlet security too, but you can't get as fine-grained.
I'll update the example we have for Aerogear, if you want to take one of
Thanks a lot, I will take a look at the documentation.
On 5/27/2014 1:19 PM, Bruno Oliveira wrote:
>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
> (on UPS)
>- 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 to set
>>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
>>>permissions. The odd thing is: after login I'm immediately kicked out of
>>>admin, probably I'm doing something wrong for sure, but I couldn't
>>>This is the piece of code being tested:
>>>And this is the log file:
>>>https://gist.github.com/abstractj/eb75d6210eb29394d139. 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
JBoss, a division of Red Hat