Skip to content

Add example command and update note on SHA1

Christopher Guitarte requested to merge cguitarte-master-patch-04310 into master

What does this MR do and why?

Describe in detail what your merge request does and why.

What

I added a snippet in our docs to recommend how to create a SHA1 certificate fingerprint to the Google Workspace section and a reference to Google Workspace as one IDP that needs the fingerprint converted to SHA1 where a customer is shown how to configure GitLab with the IDP details.

Why

After sharing the docs to a customer during an onboarding check-in call, they provided the following feedback:

By default google's certs are generated with a SHA256 fingerprint, gitlab only takes a SHA1 so it has to be converted. The documentation touches on this but I feel it is placed in the wrong place, it should be placed below the picture and also give an example code such as from google's documentation (https://support.google.com/a/answer/6342198?hl=en&fl=1) openssl x509 -noout -fingerprint -sha256 -inform pem -in "GoogleIDPCertificate-domain.com.pem" When I was whizzing by the setup this is easily missed and adding this code would help alert folks the need to convert

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports