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
In our use case, using an internal OIDC provider causes x509 certificate verification failure, because the TLS certificate is signed by an internal CA. My proposal is adding an optional parameter (TlsVerify=false) for disabling TLS verification when interacting with some OIDC providers. It would be even better to pass the certificate as parameter in PEM format, so fulcio can trust this certificate.
The text was updated successfully, but these errors were encountered:
Right now a typical OIDC Issuer config would look like this:
"https://keycloak.local/sigstore-realm": { "IssuerURL": "https://key cloak.local/sigstore-realm", "ClientID": "sigstore", "Type": "email" }
In our use case, using an internal OIDC provider causes x509 certificate verification failure, because the TLS certificate is signed by an internal CA. My proposal is adding an optional parameter (TlsVerify=false) for disabling TLS verification when interacting with some OIDC providers. It would be even better to pass the certificate as parameter in PEM format, so fulcio can trust this certificate.
The text was updated successfully, but these errors were encountered: