<div dir="ltr">Hi Bill,<div><br></div><div>ok, so 4.3 seems to be the way to go for us. Did I understand you correctly that keycloak will continue to support this?</div><div><br></div><div>Cheers,</div><div>Nils</div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 4:39 PM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You could use section 4.1 (Auth code grant) or 4.3 (Resource Owner<br>
Password Credentials Grant) with any OAuth library. 4.1 will require a<br>
browser. 4.3 doesn't.<br>
<br>
We will always support OAuth 2.0 through OpenID Connect.<br>
<div class=""><br>
On 4/14/2014 10:34 AM, Nils Preusker wrote:<br>
> Hi Bill,<br>
><br>
> I'm familiar with the examples, however I'm looking for a way to grant<br>
> third-party clients access to my API. Since they could be written in a<br>
> variety of languages, I'd like them to be able to obtain a token in a<br>
> defined way without being dependent on Keycloak.<br>
><br>
> I suppose the approach Marek mentioned (OAuth spec section 4.3) should<br>
> do the trick though (as long as you are planning to continue supporting it).<br>
><br>
> Cheers,<br>
> Nils<br>
><br>
><br>
> On Mon, Apr 14, 2014 at 3:32 PM, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a><br>
</div><div class="">> <mailto:<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>>> wrote:<br>
><br>
> Bearer token security. Take a look at the examples, specifically the<br>
> database-service. This is a pure REST service secured by keyloak.<br>
><br>
> At the moment, we only have support for JBoss/Wildfly, but it wouldn't<br>
> take much to write an adapter for another java environment.<br>
><br>
> On 4/12/2014 1:09 PM, Nils Preusker wrote:<br>
> > Hi all,<br>
> ><br>
> > I'm trying to figure out how I could use keycloak to secure a<br>
> REST API<br>
> > that is used bu a pure backend REST client. Do you have any<br>
> > recommendations for that (i.e. API keys)?<br>
> ><br>
> > Cheers,<br>
> > Nils<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > keycloak-user mailing list<br>
</div>> > <a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>><br>
<div class="">> > <a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
> ><br>
><br>
> --<br>
> Bill Burke<br>
> JBoss, a division of Red Hat<br>
> <a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
> _______________________________________________<br>
> keycloak-user mailing list<br>
</div>> <a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
><br>
><br>
> _______________________________________________<br>
> keycloak-user mailing list<br>
> <a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
><br>
<br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
</div></div></blockquote></div><br></div>