Keycloak

[John Francis]

I installed Keycloak on the linux server, but keycloak does not launch (?)

installed:

:/# docker run -p 8180:8180 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=admin quay.io/keycloak/keycloak:20.0.2 start-dev

Updating the configuration and installing your custom providers, if any. Please wait.

2023-01-10 18:20:35,831 INFO  [io.quarkus.deployment.QuarkusAugmentor] (main) Quarkus augmentation completed in 18029ms

2023-01-10 18:20:40,001 INFO  [org.keycloak.quarkus.runtime.hostname.DefaultHostnameProvider] (main) Hostname settings: Base URL: <unset>, Hostname: <request>, Strict HTTPS: false, Path: <request>, Strict BackChannel: false, Admin URL: <unset>, Admin: <request>, Port: -1, Proxied: false

2023-01-10 18:20:42,842 WARN  [io.quarkus.agroal.runtime.DataSources] (main) Datasource <default> enables XA but transaction recovery is not enabled. Please enable transaction recovery by setting quarkus.transaction-manager.enable-recovery=true, otherwise data may be lost if the application is terminated abruptly

2023-01-10 18:20:44,232 WARN  [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal

2023-01-10 18:20:44,528 WARN  [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled

2023-01-10 18:20:44,560 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'

2023-01-10 18:20:45,193 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.10.Final

2023-01-10 18:20:46,132 INFO  [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: node_837969, Site name: null

2023-01-10 18:20:49,458 INFO  [org.keycloak.quarkus.runtime.storage.legacy.liquibase.QuarkusJpaUpdaterProvider] (main) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml

2023-01-10 18:20:54,394 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener

2023-01-10 18:20:54,406 INFO  [org.keycloak.services] (main) KC-SERVICES0050: Initializing master realm

2023-01-10 18:20:56,910 INFO  [io.quarkus] (main) Keycloak 20.0.2 on JVM (powered by Quarkus 2.13.3.Final) started in 20.728s. Listening on: http://0.0.0.0:8080

2023-01-10 18:20:56,911 INFO  [io.quarkus] (main) Profile dev activated.

2023-01-10 18:20:56,911 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, hibernate-orm, jdbc-h2, jdbc-mariadb, jdbc-mssql, jdbc-mysql, jdbc-oracle, jdbc-postgresql, keycloak, logging-gelf, narayana-jta, reactive-routes, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-health, smallrye-metrics, vault, vertx]

2023-01-10 18:20:57,731 INFO  [org.keycloak.services] (main) KC-SERVICES0009: Added user 'admin' to realm 'master'

2023-01-10 18:20:57,739 WARN  [org.keycloak.quarkus.runtime.KeycloakMain] (main) Running the server in development mode. DO NOT use this configuration in production.

 launch:

http://xx.xxx.xxx.xxx:8080/auth

cBioPortal Logo
Sorry, this page doesn't exist.
Return to homepage

[John Francis]

anyone?

[John Reber]

Hi John,

 

I’m wondering about the line stating it started on http://0.0.0.0:8080.  DNS wise 0.0.0.0 will not translate to anything:

 

2023-01-10 18:20:56,910 INFO  [io.quarkus] (main) Keycloak 20.0.2 on JVM (powered by Quarkus 2.13.3.Final) started in 20.728s. Listening on: http://0.0.0.0:8080.

 

John

------

John Reber
Systems Development Manager

Philadelphia, PA 19107
John....@jefferson.edu
KimmelCancerCenter.org

 

 

From: cbiop...@googlegroups.com <cbiop...@googlegroups.com> on behalf of John Francis <jmf...@gmail.com>
Date: Wednesday, January 18, 2023 at 09:04
To: cBioPortal for Cancer Genomics Discussion Group <cbiop...@googlegroups.com>
Subject: [cbioportal] Re: Keycloak

You don't often get email from jmf...@gmail.com. Learn why this is important

WARNING:  External Email - This email originated outside of Jefferson. DO NOT CLICK links or attachments unless you recognize the sender and are expecting the email. Click the "Report Phish" button on your Outlook toolbar to alert IS&T.

 

--
You received this message because you are subscribed to the Google Groups "cBioPortal for Cancer Genomics Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cbioportal+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cbioportal/2e3d47a5-ed27-44e9-8688-37551525cd99n%40googlegroups.com.

The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.

[Benjamin Gross]

Hi John,

I’m guessing from your email that you are following the procedure found on this keycloak page:

https://www.keycloak.org/getting-started/getting-started-docker

After you executer the docker run command, I think you are following the link on that page?

which resolves to:

http://localhost:8080/admin

But that is the port the cBioPortal application is listening on.  What you want to do is go to:

http://localhost:8180/admin

Which is where you’ve pointed keycloak in your docker run command.

Let me know if this is not the case.

Best,

-Benjamin

[John Francis]

Yes, it is listening on 8180....

CONTAINER ID   IMAGE                              COMMAND                  CREATED        STATUS                 PORTS                                                                                                                                                                        NAMES
b5953684fd84   quay.io/keycloak/keycloak:20.0.3   "/opt/keycloak/bin/k…"   19 hours ago   Up 19 hours            8080/tcp, 8443/tcp, 0.0.0.0:8180->8180/tcp, :::   8180->8180/tcp   nice_solomon

When I try to launch the app, I get this error:  (The cbioportal application launches successfully)  

http://xx.xxx.xxx.xxx:8180/admin

This site can’t be reached

xx.xxx.xxx.xxx refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

[Benjamin Gross]

This sounds like a firewall issue.  I just remember, you are not actually changing the port that keycloak is listening on in your docker command, thats just making the host port route to the correct docker container port.

I did a quick google, and it looks like you can add a parameter to your docker command to set the keycloak port:

--hostname-port=3000

docker run -p 8180:8180 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=admin quay.io/keycloak/keycloak:20.0.2 start-dev —hostname-port=8180

I found this here

https://www.keycloak.org/server/containers

Let me know how it goes.

-B

To view this discussion on the web visit https://groups.google.com/d/msgid/cbioportal/1673ed70-6907-4daf-a7cb-556d1fa0aed7n%40googlegroups.com.

[John Francis]

I re-ran the docker command with that extra parameter...Keycloak still does not launch. 

CONTAINER ID   IMAGE                              COMMAND                  CREAT                                                                                                             ED         STATUS                 PORTS                 NAMES                                                                                                                                      

544f5f8cde69   quay.io/keycloak/keycloak:20.0.3   "/opt/keycloak/bin/k…"   9 minutes ago   Up 9 minutes           8080/tcp, 8443/tcp, 0.0.0.0:8180->8180/tcp, :::8180->8180/tcp   epic_ellis

[Benjamin Gross]

If you bring down the cBioPortal service, can you access keycloak using default options?

To view this discussion on the web visit https://groups.google.com/d/msgid/cbioportal/f7ff259b-4ec9-4e0d-be9d-032d6d5d39cfn%40googlegroups.com.

[John Francis]

stopped cbioportal container .....

http://10.168.128.164:8180/admin

This site can’t be reached

10.168.128.164 refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

[Benjamin Gross]

If you are not running your keycloak container on your localhost, this can be a connectivity/firewall issue between where you browser is running and where your keycloak container is running.   Is this your setup?

To view this discussion on the web visit https://groups.google.com/d/msgid/cbioportal/68aba9f5-1d58-4c38-bf78-0292b672f032n%40googlegroups.com.

[John Francis]

Yes, keycloak is running on the localhost on port 8180

[Benjamin Gross]

Oh, but I see an IP address of 10.168.128.164 in your previous email.  In any event, if you are launching Keycloak on localhost without the cBioPortal service running (to remove any conflict over the port), and still cannot access the Keycloak admin page, I think you need to check with Keycloak user support.  I don’t know what else it could be other than a firewall issue.

Sorry I couldn’t be of more help.

-Benjamin

To view this discussion on the web visit https://groups.google.com/d/msgid/cbioportal/a67b6d5f-d56f-4c3a-b28c-ef7165d6ea42n%40googlegroups.com.

[John Francis]

Thank you