Replies: 1 comment
|
Heya, from your logs, it looks like your selfsigned certificate isn’t trusted in backend... but you said it's working for your other services... so are you sure your cert is configured properly? And added in trust store? Does the OIDC discovery actually work if you curl it from inside the container? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey! I recently came across this project, thought it looked interesting and decided to give it a try.
Setting it up with the developer credentials was straightforward, and after briefly exploring the web front end, I wanted to try out authentication with PocketID.
I quickly spun up a fresh Docker instance of PocketID and configured Wardrobe as a new OIDC client.
I also had to set
OIDC_HOSTandOIDC_HOST_IPmanually as settingLOCAL_DNSdid not work for me.I also set
OIDC_SKIP_SSL_VERIFYto true, as I am using self-signed certificates for my environment.Unfortunately, when I try to log in to Wardrobe, I get the following error message saying that it cannot verify the certificate, even though it should skip the verification.
I have successfully used the self-signed certificates I use for other services as well. In addition, the root CA certificate is installed on all my client devices, so the connection from my browser is encrypted and established without any error messages.
Am I missing something? Any help or support would be much appreciated.
All reactions