Hi,
I'm currently trying to set up keycloak with cbioportal, and I'm running
into some issues with reverse proxying the keycloak part of the
authentication process.
I've installed both kc and bioportal with docker as per the
instructions, and I'm using nginx as my web server. My reverse proxy
config looks like this:
server {
listen 80;
server_name cbioportal.domain;
location / {
proxy_pass
http://localhost:8180;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_cache_bypass $http_upgrade;
}
location /data {
proxy_pass
http://localhost:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_cache_bypass $http_upgrade;
}
}
When I point my browser at cbioportal.domain/data, it redirects to
cbioportal.domain, and I get a keycloak 404 message. I've defined this
address in the portal.properties file, using the
saml.sp.metadata.entitybaseurl directive. The addresses are in my
/etc/hosts file for testing purposes. The 404 is at an address ending
"saml/discovery?entityID=cbioportal&returnIDParam=idp".
Is there some part of the necessary configuration for this I'm missing?
Thanks in advance for any pointers.
Thanks,
Jamie O'Connor