OAuth with self-signed certificate #1974

Closed
opened 2026-03-22 13:48:59 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @3isenHeiM on GitHub (Jul 18, 2024).

Description

Hi, I'm using Vikunja with Autnetik as SSO provider. Both are running on the same machine, with self-signed certificates to each.

Apparently the SSO (Authentik) must have a signed certificate, because I'm getting this error :

vikunja-server  | 2024-07-18T13:42:33.280188937Z: ERROR ▶ openid/GetAllProviders 0e1 Error while getting openid provider authentik Login: Get "https://auth.<FQDN>/application/o/vikunja/.well-known/openid-configuration": tls: failed to verify certificate: x509: certificate signed by unknown authority

How can I circumvent this ? I haven't found a flag in the configfile to skip the TLS vertificate verification...

Thanks !

Vikunja Version

v0.24.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @3isenHeiM on GitHub (Jul 18, 2024). ### Description Hi, I'm using Vikunja with Autnetik as SSO provider. Both are running on the same machine, with self-signed certificates to each. Apparently the SSO (Authentik) must have a signed certificate, because I'm getting this error : ```log vikunja-server | 2024-07-18T13:42:33.280188937Z: ERROR ▶ openid/GetAllProviders 0e1 Error while getting openid provider authentik Login: Get "https://auth.<FQDN>/application/o/vikunja/.well-known/openid-configuration": tls: failed to verify certificate: x509: certificate signed by unknown authority ``` How can I circumvent this ? I haven't found a flag in the configfile to skip the TLS vertificate verification... Thanks ! ### Vikunja Version v0.24.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Jul 18, 2024):

There is no option in Vikunja to disable certificate validation. You should add the root CA of your self-signed certificate to the trust store on your OS and then mount it into the docker container (From the log message, it looks like you're using docker, if not you don't need to mount it) into one of these locations.

Another option would be Let's Encrypt.

@kolaente commented on GitHub (Jul 18, 2024): There is no option in Vikunja to disable certificate validation. You should add the root CA of your self-signed certificate to the trust store on your OS and then mount it into the docker container (From the log message, it looks like you're using docker, if not you don't need to mount it) into one of [these locations](https://go.dev/src/crypto/x509/root_linux.go). Another option would be Let's Encrypt.
Author
Owner

@3isenHeiM commented on GitHub (Jul 19, 2024):

Thanks for the hint ;)

I indeed mounted my custom CA certificate in /etc/ssl/certs/<ca-cert.pem> in the docker compose file, and it solved the issue.

@3isenHeiM commented on GitHub (Jul 19, 2024): Thanks for the hint ;) I indeed mounted my custom CA certificate in `/etc/ssl/certs/<ca-cert.pem>` in the docker compose file, and it solved the issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1974