<div dir="ltr">not sure, perhaps you might ask on the Keycloak list for this adapter issue?</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 10, 2016 at 3:52 PM, mridul <span dir="ltr"><<a href="mailto:mridul.choudhury@skymetweather.com" target="_blank">mridul.choudhury@skymetweather.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
I am successfully running a test for<br>
aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8 in my<br>
office network with perfect access , registration of devices and messaging<br>
by using <a href="https://my_pub_ip:8443/ag-push" rel="noreferrer" target="_blank">https://my_pub_ip:8443/ag-push</a>. So far so good, now last Monday I<br>
set up the same environment (for production purposes) at Amazone EC2<br>
instance and tested it with Self signed keys. I am able to access<br>
<a href="https://amazone_pub_ip:8443" rel="noreferrer" target="_blank">https://amazone_pub_ip:8443</a> , it displays me the wildfly index page. The<br>
moment I access /ag-push in amazone ec2 instance I get a run time exception<br>
as below :<br>
<br>
18:16:20,702 ERROR [io.undertow.request] (default task-22) UT005023:<br>
Exception handling request to /ag-push/: java.lang.RuntimeException: Unable<br>
to resolve realm public key remotely<br>
at<br>
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:136)<br>
at<br>
org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:85)<br>
at<br>
org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:74)<br>
at<br>
org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:50)<br>
at<br>
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)<br>
at<br>
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)<br>
at<br>
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284)<br>
at<br>
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)<br>
at<br>
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)<br>
at<br>
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)<br>
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)<br>
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)<br>
at<br>
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)<br>
at<br>
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)<br>
at java.lang.Thread.run(Thread.java:745)<br>
Caused by: java.net.ConnectException: Connection timed out<br>
at java.net.PlainSocketImpl.socketConnect(Native Method)<br>
at<br>
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)<br>
at<br>
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)<br>
at<br>
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)<br>
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)<br>
at java.net.Socket.connect(Socket.java:589)<br>
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)<br>
at<br>
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)<br>
at<br>
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)<br>
at<br>
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)<br>
at<br>
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)<br>
at<br>
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)<br>
at<br>
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)<br>
at<br>
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)<br>
at<br>
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)<br>
at<br>
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)<br>
at<br>
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)<br>
at<br>
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)<br>
at<br>
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:107)<br>
<br>
<br>
Please share some insight to this issue<br>
<br>
Thanks.<br>
Mridul.<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-users.1116366.n5.nabble.com/SSL-issue-at-Amazon-EC2-With-aerogear-unifiedpush-server-1-2-0-alpha-1-on-Wildfly-10-Java-8-tp718.html" rel="noreferrer" target="_blank">http://aerogear-users.1116366.n5.nabble.com/SSL-issue-at-Amazon-EC2-With-aerogear-unifiedpush-server-1-2-0-alpha-1-on-Wildfly-10-Java-8-tp718.html</a><br>
Sent from the aerogear-users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Aerogear-users mailing list<br>
<a href="mailto:Aerogear-users@lists.jboss.org">Aerogear-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-users</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div>