keycloak

have a problems configuring keycloak behind my apache server, Mixed Content: The page at ' https://dev.mydomain.com/auth/admin/master/console/ ' was loaded over HTTPS, but requested an insecure script ' http://dev.mydomain.com/auth/resources/1.7.0.final/admin/keycloak/js/controllers/groups.js '. This request has been blocked; the content must be served over HTTPS. My apache configuration is, ServerName dev.mydomain.com ServerAdmin dev@mydomain.com SSLEngine on SSLCertificateFile /opt/mydomain/domains/dev.mydomain.com/apache/dev.mydomain.com.crt SSLCertificateKeyFile /opt/mydomain/domains/dev

I have a very special requirements in my Spring Boot web application: I have internal and external users. Internal users login to the web application by using keycloak authentication (they can work in the web application), but our external users login by simple Spring Boot authentication (what they can do is just to download some files generated by web application) What I want to do is to have multiple authentication model: all the path except /download/* to be authenticated by our Keycloak authentication, but the path /download/* to be authenticated by SpringBoot basic authentication. At the

I have a sample app which correctly secures the rest api locally without nginx. Now when I put this in production behind a nginx proxy it does not work. No errors. It allows all request. Front end serer with ssl is https://frontend.com Back end server with ssl is https://backend.com Keycloak proxy forward is true Front end server(node server on 9000) <-> NGINX <-> Keycloak (running on 8180) nginx file sample upstream keycloak_server { server localhost:8180; } upstream node_server { server localhost:9000; } location /auth/ { proxy_pass http://keycloak_server; proxy_http_version 1.1; proxy_set

I want to use keycloak to authenticate my users in our Superset environment. Superset is using flask-openid, as implemented in flask-security: http://flask-appbuilder.readthedocs.io/en/latest/_modules/flask_appbuilder/security/manager.html https://pythonhosted.org/Flask-OpenID/ To enable a different user authentication than the regular one (database), you need to override the AUTH_TYPE parameter in your superset_config.py file. You will also need to provide a reference to your openid-connect realm and enable user registration. As I understand, it should look something like this: from flask

How can I set the docker keycloak base url as parameter ? I have the following nginx reverse proxy configuration: server { listen 80; server_name example.com; location /keycloak { proxy_pass http://example.com:8087/; } } When I try to access http://example.com/keycloak/ I got a keycloak http redirect to http://example.com/auth/ instead of http://example.com/keycloak/auth/ Any ideas? Just tested that @home, and actually multiple configuration additions are needed: 1/ Run the keycloak container with env -e PROXY_ADDRESS_FORWARDING=true as explained in the docs, this is required in a proxy way of