You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When OIDC_TLS_CACERTFILE (variable found in github issues here) is set up to point to a certificate created by a two tier CA, RomM SSO with Authentik is not working anymore. My homelab is using an offline RootCA with EnterpriseCAs to create the actual certificates. Compose and .env are at the end of the issue. Without OIDC_TLS_CACERTFILE set, Authentik and RomM work perfectly. Current workaround is to use Authentik self signed certificate.
To Reproduce
Steps to reproduce the behavior:
Set up working Authentik / RomM SSO (provided compose / .env work)
Change self signed certificate in Authentik to one provided by EnterpriseCA (certificate works with other containers like Nextcloud AIO)
Try to connect using sso to RomM
ISSUE HERE
4. Get Internal Server Error, with "httpx.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)" in the container logs when using OIDC_TLS_CACERTFILE = /romm/certs or a lot of formats (like .p7b)
Get Internal Server Error, with "ssl.SSLError: [X509: NO_CERTIFICATE_OR_CRL_FOUND] no certificate or crl found (_ssl.c:4096)" when using OIDC_TLS_CACERTFILE = /romm/certs/rootCA.crt
DEBUG STEPS HERE
5. Change Authentik Sign certificate to self signed.
6. Still get an internal server error for the same reasons.
7. Comment OIDC_TLS_CACERTFILE from compose and .env and restart stack.
8. Everything works again.
9.Change Authentik Sign cerficate to nothing, get "ValueError: Invalid key set format" (just to say that communication between Authentik and Romm on the certificate seems to be working perfectly fine)
Expected behavior
In step 4, Romm would trust the RootCA => EnterpriseCA chain provided. Romm verify the Authentik certificate provided by EnterpriseCA, RomM would log the user using Authentik SSO after the verification is ok.
Screenshots
I could add screenshot if necessary.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser Firefox
Version latest
Additional context
I tried OIDC_TLS_CACERTFILE with multiple file formats .crt, .pem, .p7b, .cer. I also tried pointing directly to the directory /romm/certs/.
Tried certificates containing those chains:
RootCA => EnterpriseCA => Authentik
RootCA => EnterpriseCA
RootCA
Other systems with certs have been working (exemple NextCloud AIO), they point directly to the /certs folder and automatically trust everything in there.
I could add the full stacktrace from the container logs if helpful. There is a bit more plumbing in the homelab that I could share if necessary (reverseproxy, dns etc) but they do not seem relevant since SSO works with self signed authentik certificate.
RomM version
v3.7.3
Describe the bug
When OIDC_TLS_CACERTFILE (variable found in github issues here) is set up to point to a certificate created by a two tier CA, RomM SSO with Authentik is not working anymore. My homelab is using an offline RootCA with EnterpriseCAs to create the actual certificates. Compose and .env are at the end of the issue. Without OIDC_TLS_CACERTFILE set, Authentik and RomM work perfectly. Current workaround is to use Authentik self signed certificate.
To Reproduce
Steps to reproduce the behavior:
ISSUE HERE
4. Get Internal Server Error, with "httpx.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)" in the container logs when using OIDC_TLS_CACERTFILE = /romm/certs or a lot of formats (like .p7b)
Get Internal Server Error, with "ssl.SSLError: [X509: NO_CERTIFICATE_OR_CRL_FOUND] no certificate or crl found (_ssl.c:4096)" when using OIDC_TLS_CACERTFILE = /romm/certs/rootCA.crt
DEBUG STEPS HERE
5. Change Authentik Sign certificate to self signed.
6. Still get an internal server error for the same reasons.
7. Comment OIDC_TLS_CACERTFILE from compose and .env and restart stack.
8. Everything works again.
9.Change Authentik Sign cerficate to nothing, get "ValueError: Invalid key set format" (just to say that communication between Authentik and Romm on the certificate seems to be working perfectly fine)
Expected behavior
In step 4, Romm would trust the RootCA => EnterpriseCA chain provided. Romm verify the Authentik certificate provided by EnterpriseCA, RomM would log the user using Authentik SSO after the verification is ok.
Screenshots
I could add screenshot if necessary.
Desktop (please complete the following information):
Additional context
I tried OIDC_TLS_CACERTFILE with multiple file formats .crt, .pem, .p7b, .cer. I also tried pointing directly to the directory /romm/certs/.
Tried certificates containing those chains:
Other systems with certs have been working (exemple NextCloud AIO), they point directly to the /certs folder and automatically trust everything in there.
I could add the full stacktrace from the container logs if helpful. There is a bit more plumbing in the homelab that I could share if necessary (reverseproxy, dns etc) but they do not seem relevant since SSO works with self signed authentik certificate.
Docker compose:
stack.env:
The text was updated successfully, but these errors were encountered: