[full-cosmo-docker] Unable to login to demo Studio due to HTTPS requirement
Component(s)
studio
Component version
Cloned main (a94ffee12c53f983dbcdc3cc5115176ac095b813)
wgc version
0.94.1
controlplane version
latest as of a94ffee12c53f983dbcdc3cc5115176ac095b813
router version
latest as of a94ffee12c53f983dbcdc3cc5115176ac095b813
What happened?
Description
I'm evaluating Wundergraphs Cosmo and wanted to run full platform locally as per https://cosmo-docs.wundergraph.com/self-hosted#docker and https://github.com/wundergraph/cosmo/blob/main/examples/full-cosmo-docker/README.md
Platform starts up but I cannot login to UI due to https requirement
Steps to Reproduce
- clone repo
- go to examples/full-cosmo-docker
- run
./start.sh - open http://localhost:3000 as instructed
- try to login by using
Login with email
Expected Result
I would like to be able to login with provided demo credentials. I expect the demo to setup self-signed certificates so UI can be accessed, or disable SSL requirement
Actual Result
You will be greeted with https error:
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Package Manager: pnpm, npm, yarn, etc Compiler(if manually compiled): (e.g., "go 14.2")
Router configuration
Router execution config
Log output
Additional context
No response
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. The roadmap is driven by our customers and we have to prioritize issues that are important to them. You can influence the priority by becoming a customer. Please contact us here.
Hi @gustaff-weldon, Could you please confirm, are you using docker-desktop? If so, which version?
Could you also try to set sslRequired to NONE under docker/keycloak/realm.json, then destroy and start the demo again, to see it works?
Hi @miklosbarabas yes, I'm using Docker desktop, version 4.48.0 (207573)
I think the error stems from the fact that Keycloak from certain version (26?) enforces HTTPS
I have already tried setting sslRequired to NONE in the file you have mentioned, as well as passing --hostname-strict false --http-enabled true via the KEYCLOAK_EXTRA_ARGS in https://github.com/wundergraph/cosmo/blob/main/docker-compose.full.yml#L149 nothing helped so far.
I start with ./start.sh and clean up with ./destroy before testing new file changes.
People suggest updating sslRequired on master realm but I have yet to find a way to do it via config/variables.
Got the cosmo login to work. After initial login failures, I was testing keycloak admin with just http://localhost:8080 and that did not work.
I have just tried with login link ie. http://localhost:3001/v1/auth/login?redirectURL=http%3A%2F%2Flocalhost%3A3000%2F and I can see the cosmo login screen and was able to login.
I will see if changes in compose are needed or was it just the NONE in cosmo realm
EDIT: change to cosmo's realm sslRequired does the job., no need to change extra args.
I still cannot access keycloak admin via localhost:8080 due to master realm requiring https (see above for updating master realm and below for screenshots)
I have the same problem. Also, bitnamilegacy/keycloak image is no longer supported. Bitnami rolled images behind paywall, at least from my understanding from the quick reading of docs. See https://hub.docker.com/r/bitnami/keycloak vs https://hub.docker.com/r/bitnamilegacy/keycloak