<div dir="ltr">It turned out to be a FW configuration issue after all. <div><br></div><div>Now that the adapters get k_logout properly, I&#39;m assuming that the way for a jee application to learn about the logout is by listening to the HttpSession, correct ?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 7, 2015 at 1:54 PM, Stian Thorgersen <span dir="ltr">&lt;<a href="mailto:stian@redhat.com" target="_blank">stian@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">Currently the trust manager is actually disabled for these requests so that won&#39;t be the problem. We have an outstanding issue to fix this.<br>
<span class="im HOEnZb"><br>
----- Original Message -----<br>
&gt; From: &quot;Hubert Przybysz&quot; &lt;<a href="mailto:h.p.przybysz@gmail.com">h.p.przybysz@gmail.com</a>&gt;<br>
&gt; To: &quot;Stian Thorgersen&quot; &lt;<a href="mailto:stian@redhat.com">stian@redhat.com</a>&gt;<br>
&gt; Cc: &quot;keycloak-user&quot; &lt;<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>&gt;<br>
</span><div class="HOEnZb"><div class="h5">&gt; Sent: Wednesday, 7 January, 2015 1:45:03 PM<br>
&gt; Subject: Re: [keycloak-user] single logout<br>
&gt;<br>
&gt; It is reachable but perhaps it is a truststore issue.<br>
&gt;<br>
&gt; Which truststore is used by the server, the one configured in jboss for<br>
&gt; https connector, or some other ?<br>
&gt;<br>
&gt; On Wed, Jan 7, 2015 at 1:25 PM, Stian Thorgersen &lt;<a href="mailto:stian@redhat.com">stian@redhat.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Looks like a configuration issue (or a bug) you should not have to<br>
&gt; &gt; implement anything as long as you use our adapters.<br>
&gt; &gt;<br>
&gt; &gt; Did you set the admin url correctly for the app? It has to be reachable<br>
&gt; &gt; from the Keycloak server. Also, if your app is behind a proxy or is<br>
&gt; &gt; clustered that can also impact on the config.<br>
&gt; &gt;<br>
&gt; &gt; ----- Original Message -----<br>
&gt; &gt; &gt; From: &quot;Hubert Przybysz&quot; &lt;<a href="mailto:h.p.przybysz@gmail.com">h.p.przybysz@gmail.com</a>&gt;<br>
&gt; &gt; &gt; To: &quot;Stian Thorgersen&quot; &lt;<a href="mailto:stian@redhat.com">stian@redhat.com</a>&gt;<br>
&gt; &gt; &gt; Cc: &quot;keycloak-user&quot; &lt;<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>&gt;<br>
&gt; &gt; &gt; Sent: Wednesday, 7 January, 2015 1:18:58 PM<br>
&gt; &gt; &gt; Subject: Re: [keycloak-user] single logout<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I&#39;m using your server-side java adapters. When I logout in one<br>
&gt; &gt; application<br>
&gt; &gt; &gt; I&#39;m getting the exception below when the server tries to logout the<br>
&gt; &gt; second<br>
&gt; &gt; &gt; application (which led me to think I need to implement something).<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Logout for application &#39;app-2&#39; failed:<br>
&gt; &gt; &gt; org.apache.http.conn.HttpHostConnectException: Connection to https:/<br>
&gt; &gt; &gt; <a href="http://xx.xx.net" target="_blank">xx.xx.net</a> refused<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:151)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)<br>
&gt; &gt; &gt; [httpclient-4.2.1-redhat-1.jar:4.2.1-redhat-1]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.execute(ApacheHttpClient4Executor.java:182)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:39)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor.execute(AcceptEncodingGZIPInterceptor.java:40)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:45)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; org.jboss.resteasy.client.ClientRequest.execute(ClientRequest.java:444)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.jboss.resteasy.client.ClientRequest.httpMethod(ClientRequest.java:688)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at org.jboss.resteasy.client.ClientRequest.post(ClientRequest.java:572)<br>
&gt; &gt; &gt; [resteasy-jaxrs-2.3.7.Final-redhat-2.jar:2.3.7.Final-redhat-2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.services.managers.ResourceAdminManager.sendLogoutRequest(ResourceAdminManager.java:275)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.services.managers.ResourceAdminManager.logoutClientSessions(ResourceAdminManager.java:207)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.services.managers.ResourceAdminManager.logoutClientSession(ResourceAdminManager.java:167)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.protocol.oidc.OpenIDConnect.backchannelLogout(OpenIDConnect.java:143)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.services.managers.AuthenticationManager.logout(AuthenticationManager.java:97)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.protocol.oidc.OpenIDConnectService.logout(OpenIDConnectService.java:994)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at<br>
&gt; &gt; &gt;<br>
&gt; &gt; org.keycloak.protocol.oidc.OpenIDConnectService.logout(OpenIDConnectService.java:927)<br>
&gt; &gt; &gt; [keycloak-services-1.1.0.Beta2.jar:1.1.0.Beta2]<br>
&gt; &gt; &gt; at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
&gt; &gt; &gt; [rt.jar:1.7.0_72]<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On Wed, Jan 7, 2015 at 12:53 PM, Stian Thorgersen &lt;<a href="mailto:stian@redhat.com">stian@redhat.com</a>&gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; What adapters are you using? Our adapters already have built-in support<br>
&gt; &gt; &gt; &gt; for this. Server-side adapters (JEE) uses the admin url, while<br>
&gt; &gt; client-side<br>
&gt; &gt; &gt; &gt; (JS) uses a special iframe to detect logout.<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; ----- Original Message -----<br>
&gt; &gt; &gt; &gt; &gt; From: &quot;Hubert Przybysz&quot; &lt;<a href="mailto:h.p.przybysz@gmail.com">h.p.przybysz@gmail.com</a>&gt;<br>
&gt; &gt; &gt; &gt; &gt; To: &quot;keycloak-user&quot; &lt;<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>&gt;<br>
&gt; &gt; &gt; &gt; &gt; Sent: Wednesday, 7 January, 2015 12:19:12 PM<br>
&gt; &gt; &gt; &gt; &gt; Subject: [keycloak-user] single logout<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; Hi,<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; I&#39;m looking for information on how to implement single logout across<br>
&gt; &gt; &gt; &gt; &gt; applications in the realm. There is an Admin URL setting per<br>
&gt; &gt; application<br>
&gt; &gt; &gt; &gt; in<br>
&gt; &gt; &gt; &gt; &gt; the realm admin GUI which is to be set if the application supports<br>
&gt; &gt; &quot;the<br>
&gt; &gt; &gt; &gt; &gt; adapter REST API&quot;, but I failed to find any information about this<br>
&gt; &gt; API.<br>
&gt; &gt; &gt; &gt; Is<br>
&gt; &gt; &gt; &gt; &gt; this the API to use for single logout ?<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; Br / Hubert.<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; &gt; &gt; keycloak-user mailing list<br>
&gt; &gt; &gt; &gt; &gt; <a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
&gt; &gt; &gt; &gt; &gt; <a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt;<br>
</div></div></blockquote></div><br></div>