FIXED: Allow custom omniauth provider configuration for GitLab

General MR

Summary

Solves issue #1088 (closed), and corrects !1382 (merged), allows GitLab SSO to be used with non-keycloak SSO (including Okta)

Relevant logs/screenshots

(Include any relevant logs/screenshots)

BB Processes

Add labels for affected packages so that they are deployed in CI as well as a status label:

Be sure to assign to yourself:

Once it is ready for review switch the status and assign reviewers:

added statusreview label

requested review from @runyontr, @kevin.wilder, and @micah.nagel

assigned to @charles.bushong

mentioned in merge request !1382 (merged)

added 19 commits

• 80fbf70d...d6629ada - 18 commits from branch master
• fd3543a3 - Merge branch 'master' into gitlab-broader-sso-support

Compare with previous version

Otherwise LGTM, tested with Keycloak and all the defaults work as expected still.

changed milestone to %1.29.0

I tested and the Keycloak SSO still works.

added 1 commit

• f6664f24 - uncomment new sso keys

Compare with previous version

added 1 commit

• f0bb915b - uncomment new sso keys

Compare with previous version

resolved all threads

added 1 commit

• 16e769f0 - uncomment new sso keys

Compare with previous version

Keycloak SSO still works. LGTM

approved this merge request

merged

mentioned in commit 23199695