Removal of the Crowd OmniAuth provider in GitLab 16.0 (omniauth_crowd)

Here Deprecations by version | GitLab it is announced that with Gitlab 16.0 the Crowd OmniAuth provider (omniauth_crowd) will be removed.

Unfortunately, I can’t find any detailed information on how affected customers should deal with this.

If we switch to a different authentication provider in the future (e.g. Azure AD), how do I ensure in Gitlab that the users automatically map with the old crowd user.

Do I just need to make sure that the user’s email address is the same?

I also wonder how to test this in advance. Is it possible to activate two authentication providers at the same time and test the switch to the new provider with selected users?


1 Like