<div dir="ltr">Bill,<div><br><div>I have rc1 and not rc2, let me check if it works in the newer version. It may be the version.</div><div><br></div><div>Thanks</div><div>Sam</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 5, 2014 at 3:13 PM, Red Samh <span dir="ltr">&lt;<a href="mailto:redsamh@gmail.com" target="_blank">redsamh@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Bill,<div><br></div><div>I am able to get the example to work and it is fine if I am calling REST service to any other REST service (any number of hops). Does it work if you try to access another web application (just submit a form, access content or anything) that is authenticated by Keycloak or Are you able to make a call from the REST Service to a web application that is configured with Keycloak?</div><div><br></div><div>See attached explanation.</div><div><br></div><div>Thanks</div><div>Sam</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 5, 2014 at 2:41 PM, Bill Burke <span dir="ltr">&lt;<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You&#39;re going to have to elaborate on your problem as I was unable to reproduce it.<br>
<br>
I took examples/preconfigured-demo/<u></u>customer-app and added the database/ projects Java files to it.  I was able to deploy this application and do both web and bearer auth from the same war.<br>
<br>
Are you using latest Keycloak?  1.0-rc2?<span><br>
<br>
On 9/5/2014 1:31 PM, Red Samh wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
<br>
Thanks Bill, much appreciated. Is there something I can do in the<br>
interim even if it is a hack?. I was looking at adapter code or even<br>
something I can hardcode in the rest service to pull out the user<br>
information and make the call to the back end application?<br>
<br>
Thanks<br>
Sam<br>
<br>
On Sep 5, 2014 1:19 PM, &quot;Bill Burke&quot; &lt;<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a><br></span><span>
&lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;&gt; wrote:<br>
<br>
    A pure servlet filter is on the roadmap, but it wouldn&#39;t be as<br>
    seemlessly integrated.  I&#39;ll take a look at your problem.<br>
<br>
    On 9/5/2014 11:59 AM, Red Samh wrote:<br>
<br>
<br>
        Eap 6.x, it would be nice if i could generalize to any war<br>
        deployed to<br>
        to tomcat or jetty.<br>
<br>
        Thanks<br>
        Sam<br>
<br>
        On Sep 5, 2014 11:51 AM, &quot;Bill Burke&quot; &lt;<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a><br>
        &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;<br></span><div><div>
        &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a> &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;&gt;&gt; wrote:<br>
<br>
             Wildfly or JBoss EAP 6.x or JBoss AS 7.1?<br>
<br>
<br>
             On 9/5/2014 11:49 AM, Red Samh wrote:<br>
<br>
                 Bill,<br>
<br>
                 Thanks for the reply.<br>
<br>
                 Yes it works when I have to call REST to another REST<br>
        service<br>
                 and any<br>
                 number of hops. The problem is calling a full  fledged<br>
                 application from<br>
                 a REST service that I have the issue. When it is an<br>
        application<br>
                 that is<br>
                 both Web App + REST and I add the authorization header<br>
        (bearer)<br>
                 I get an<br>
                 unauthorized 401 (blackbox in the attachment).<br>
<br>
                 Thanks<br>
                 Sam<br>
<br>
<br>
                 On Fri, Sep 5, 2014 at 11:42 AM, Bill Burke<br>
        &lt;<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a> &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;<br>
                 &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a> &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;&gt;<br>
                 &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a> &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;<br>
        &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a> &lt;mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;&gt;&gt;&gt; wrote:<br>
<br>
                      Should work.  You&#39;ll have to actually describe<br>
        what your<br>
                 problem is or I<br>
                      can&#39;t help you.  I&#39;ll take a guess though:<br>
<br>
                      Keycloak doesn&#39;t propagate the Authorization<br>
        bearer token<br>
                 header<br>
                      automatically when you have multiple REST &quot;hops&quot;<br>
        between<br>
                 multiple<br>
                      servers  You&#39;ll have to obtain the access token<br>
        and set up<br>
                 the HTTP<br>
                      header manually.  The demo customer-portal example<br>
        in the<br>
                 distro does<br>
                      exactly this, so take a look at that for more details.<br>
<br>
                      On 9/5/2014 10:58 AM, Red Samh wrote:<br>
                       &gt; Hello,<br>
                       &gt;<br>
                       &gt; We have an application that is protected using<br>
        Keycloak<br>
                 and a<br>
                      user can<br>
                       &gt; access this application through a web front.<br>
        After login<br>
                 the user can<br>
                       &gt; use the functionality of the application. The<br>
                 application is also<br>
                       &gt; exposed through REST API&#39;s and is protected via<br>
        keycloak<br>
                 as part<br>
                      of the<br>
                       &gt; application and accessible only after login<br>
        into the main<br>
                      application.<br>
                       &gt;<br>
                       &gt; We have a<br>
                       &gt;<br>
                       &gt; (Step 1) Javascript application (retrieving<br>
        data from) -&gt;<br>
                       &gt;<br>
                       &gt; (Step 2) Business Application exposed as REST<br>
        API (REST<br>
                 API has<br>
                      to make<br>
                       &gt; calls to backend Application mentioned above) -&gt;<br>
                       &gt;<br>
                       &gt; (Step 3) BackEnd Application Server + REST API.<br>
                       &gt;<br>
                       &gt; Directly accessing the BackEnd Application<br>
        Server works<br>
                 fine but<br>
                      when we<br>
                       &gt; need to call the REST API from another REST<br>
        service which is<br>
                       &gt; authenticated via Keycloak we have issues.<br>
                       &gt;<br>
                       &gt; We used the existing sample to try and do a POC<br>
        but not<br>
                 sure what<br>
                      is the<br>
                       &gt; best approach to solve this issue. The part<br>
        from (Step<br>
                 1) to (Step 2)<br>
                       &gt; works and the REST API is protected using<br>
        BEARER token.<br>
                 The (Step<br>
                      2) to<br>
                       &gt; (Step 3) is a problem as in (Step 2) we only<br>
        have the BEARER<br>
                      token and<br>
                       &gt; the BackEnd Application is protected using the<br>
        full keycloak<br>
                       &gt; configuration. So The BackEnd Application<br>
        service is not<br>
                      authenticating<br>
                       &gt; by sending in only the BEARER token in the<br>
        header which<br>
                 is a full<br>
                       &gt; keycloak installation (work as only a web service).<br>
                       &gt;<br>
                       &gt; Thanks<br>
                       &gt; Sam<br>
                       &gt;<br>
                       &gt;<br></div></div>
                       &gt; ______________________________<u></u>_____________________<span><br>
                       &gt; keycloak-user mailing list<br>
                       &gt; <a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a><br>
        &lt;mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.<u></u>jboss.org</a>&gt;<br>
                 &lt;mailto:<a href="mailto:keycloak-user@lists." target="_blank">keycloak-user@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
        &lt;mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.<u></u>jboss.org</a>&gt;&gt;<br></span>
                 &lt;mailto:<a href="mailto:keycloak-user@lists" target="_blank">keycloak-user@lists</a>.<br>
        &lt;mailto:<a href="mailto:keycloak-user@lists" target="_blank">keycloak-user@lists</a>.&gt;_<u></u>___<a href="http://jboss.org" target="_blank">jboss.org</a> &lt;<a href="http://jboss.org" target="_blank">http://jboss.org</a>&gt;<br>
                 &lt;mailto:<a href="mailto:keycloak-user@lists." target="_blank">keycloak-user@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
        &lt;mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.<u></u>jboss.org</a>&gt;&gt;&gt;<br>
                       &gt;<br>
        <a href="https://lists.jboss.org/____mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/____<u></u>mailman/listinfo/keycloak-user</a><br>
        &lt;<a href="https://lists.jboss.org/__mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/keycloak-user</a><u></u>&gt;<br>
<br>
        &lt;<a href="https://lists.jboss.org/__mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/keycloak-user</a><br>
        &lt;<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/keycloak-user</a><u></u>&gt;__&gt;<span><br>
                       &gt;<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></span>
                      ______________________________<u></u>_____________________<span><br>
                      keycloak-user mailing list<br>
        <a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a> &lt;mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.<u></u>jboss.org</a>&gt;<br>
                 &lt;mailto:<a href="mailto:keycloak-user@lists." target="_blank">keycloak-user@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
        &lt;mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.<u></u>jboss.org</a>&gt;&gt;<br></span>
                 &lt;mailto:<a href="mailto:keycloak-user@lists" target="_blank">keycloak-user@lists</a>.<br>
        &lt;mailto:<a href="mailto:keycloak-user@lists" target="_blank">keycloak-user@lists</a>.&gt;_<u></u>___<a href="http://jboss.org" target="_blank">jboss.org</a> &lt;<a href="http://jboss.org" target="_blank">http://jboss.org</a>&gt;<br>
                 &lt;mailto:<a href="mailto:keycloak-user@lists." target="_blank">keycloak-user@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
        &lt;mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.<u></u>jboss.org</a>&gt;&gt;&gt;<br>
        <a href="https://lists.jboss.org/____mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/____<u></u>mailman/listinfo/keycloak-user</a><br>
        &lt;<a href="https://lists.jboss.org/__mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/keycloak-user</a><u></u>&gt;<br>
<br>
        &lt;<a href="https://lists.jboss.org/__mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/keycloak-user</a><br>
        &lt;<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/keycloak-user</a><u></u>&gt;__&gt;<span><br>
<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>
<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>
</span></blockquote><div><div>
<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>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>