<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">IMO the easiest option is to create
security-constraints in web.xml just for the REST endpoints, which
are supposed to be secured . Then the public endpoints, which
won't be mapped in web.xml can be accessed by anonymous user.<br>
<br>
Marek<br>
<br>
On 26.6.2015 01:14, Juan Diego wrote:<br>
</div>
<blockquote
cite="mid:CAJGEj6fWb9k_5txH8sMYWhRRLn=VTbd-OP=xsXk9_V+XkKi5Xw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>I have some services that should be public, I am
allowing anonymous users in my page. They should be
able to access some minor features of my site. <br>
</div>
Should I create another security-constrain for public
users, is there a way to create a public role and get a
token for that.<br>
</div>
Or that is more like creating a role for an app, maybe I
understood that part wrong.<br>
<br>
</div>
Thanks.<br>
<br>
</div>
Juan Diego<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-user">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></pre>
</blockquote>
<br>
</body>
</html>