<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007oL2SWCA0Okta Classic EngineIntegrationsAnswered2026-04-01T09:00:20.000Z2022-07-15T16:20:45.000Z2022-07-15T20:20:30.000Z

3rson (3rson) asked a question.

Is GITLAB Provisioning is required after SAML integration.

Hi,

We have done GITLAB integration in OKTA with SAML, Is it really necessary to enable Provisioning from okta end, As here we have created AD groups from there the membership flows to OKTA and users are assigned via AD groups. So do we need to do provisioning separately in OKTA.


  • k5fuw (k5fuw)

    The SAML integration will allow users to authenticate into Gitlab, but if they don't have an account in Gitlab, the sign in will fail. Provisioning automates the creation of the user accounts in Gitlab, making the end user experience much smoother. It's just a little weird (in my opinion) that SAML and Provisioning are two separate apps in Okta. You just have to assign your AD groups to both.

This question is closed.
Loading
Is GITLAB Provisioning is required after SAML integration.