<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 7.5.2015 23:41, Scott Rossillo
wrote:<br>
</div>
<blockquote
cite="mid:B5E6E774-1806-4F85-AB4F-E88F6D89B6FB@smartling.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br class="">
org.keycloak.adapters.NodesRegistrationManagement doesn’t sent a
port when it registers a node. Additionally, the KC server assumes
the cluster node is using port 8080. So even if you manually
register a node, as say localhost:9092, when you press “Test
Cluster Availability” the KC server appends port 8080 to the
request:
<div class=""><br class="">
</div>
<div class=""><a moz-do-not-send="true"
href="http://localhost:9092:8080/customer-portal/" class="">http://localhost:9092:8080/customer-portal/</a></div>
<div class=""><br class="">
</div>
<div class="">I think there are two bugs, I can open JIRAs if you
like:</div>
<div class=""><br class="">
</div>
<div class="">1. org.keycloak.adapters.NodesRegistrationManagement
should send the port the server is on</div>
</blockquote>
The JIRA already exists <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/KEYCLOAK-888">https://issues.jboss.org/browse/KEYCLOAK-888</a>
. However it's quite tricky to add port as requests to cluster are
often send via loadbalancer and hence they are on AJP port (like
8009 for example) but for backchannel requests (logout, push not
before or test cluster availability etc.) Keycloak needs to send
requests to them directly with apache http client (so using port
8080 or 8443). <br>
<br>
So for now JIRA is postponed until we have important use-case for
it.<br>
<blockquote
cite="mid:B5E6E774-1806-4F85-AB4F-E88F6D89B6FB@smartling.com"
type="cite">
<div class="">2. KC server should not assume port 8080</div>
</blockquote>
It doesn't assume 8080 but it just uses the port used in admin URL.
It uses admin URL as template, but just replaces the host with the
actual registered cluster host. The only limitation is that all
cluster hosts need to use same port (Limitation caused by
KEYCLOAK-888 )<br>
<br>
Marek<br>
<blockquote
cite="mid:B5E6E774-1806-4F85-AB4F-E88F6D89B6FB@smartling.com"
type="cite">
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Scott</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></pre>
</blockquote>
<br>
</body>
</html>