#Changing sha1 fingerprint for Let's Encrypt certificate for idp_cert_fingerprint

1 messages · Page 1 of 1 (latest)

undone meteor
#

Hello everyone,

I'm dealing with a problem that is due to the renewal of the Let's Encrypt certificate I'm using, and the new "Certificate Fingerprint (SHA1)" that it gives after renewal.
This SHA1 Fingerprint needs to be added as the value of "idp_cert_fingerprint" @ https://goauthentik.io/integrations/services/gitlab/#gitlab-configuration

Since it's changing at every renewal, I would need to update the docker-compose file manually after each renewal which isn't something I'd like to do 😅

To give an idea about the current set-up, Authentik is run in k8s, where-as Gitlab CE is run on a seperate host via docker-compose.
Authentik get's it's certificate from it's ingress + certificate in the k8s cluster, see #1075708426996424744 message for that.

How do you guys deal with this, or can you guide me to a solution for this matter?

GitLab | authentik

Support level: authentik

jaunty tangle
#

I'd use a self signed certificate for SAML

#

there is no additional security added with a CA-signed certificate since the fingerprint is already validated by the RP

#

or you can also use an OIDC provider instead of a SAML one