-
Trusted certs only used for below scenarios as mentioned in docs:
https://docs.onedev.io/administration-guide/trust-self-signed-certificates
Will change this to an improvement so that trust certs can handle these cases.
-
Name Previous Value Current Value Type
Bug
Improvement
-
Previous Value Current Value CA certificate in /opt/onedev/conf/trust-certs not trusted for OIDC or project import (gitea, SSL error)
Able to trust self-signed certs of OIDC or project import
-
-
Previous Value Current Value Able to trust self-signed certs of OIDC or project import
Able to trust self-signed certs of OIDC
-
OneDev
changed state to 'Closed' 11 months ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (0061e063)
-
OneDev
changed state to 'Released' 11 months ago
Previous Value Current Value Closed
Released
-
State changed as build OD-5887 is successful
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Hello,
As there is a feature allowing us to add CA to be trusted in /opt/onedev/conf/trust-certs, I thought it would work for OICD and for other https connections (tried to import from a gitea instance with a SSL cert signed by this CA). But in those cases it raises SSL errors:
But I have those errors (same for project import or OIDC):
If I add the certificate of the gitea instance directly, same error.
My workaround is to add the CA in the java trust-store at the start of the container, not pretty but it's working.