<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
0D50Z00008G7UegSAFOkta Classic EngineLifecycle ManagementAnswered2024-04-30T09:18:25.000Z2016-03-22T22:13:49.000Z2018-08-12T04:14:57.000Z
Using Group Push via SAML for BOX app configuration.
When you enable group push via SAML for Box, does that mean that those users who are members of that specific group will automatically have a Box account created for them in the Box tenant? To clarify, would I be able to pass our AD security groups into Box, so that they exist in Box as groups without necessarily creating new Box accounts for EVERYONE in that group?

  • r42cz (r42cz)

    When I tested this feature Okta did not initiate user account creation. I have a group being pushed containg members with and without existing Box accounts and it ignored those without accounts already.
    Selected as Best
  • Thanks for the reply Raja. I have seen the documentation you sent me, but I was still a little confused as to what actually happens on the Box end. For example, lets say I currently DO NOT have ANY BOX accounts in our Box API, if I configure the Group Push to Box via OKTA (sending My AD security group), does that mean that the group push initiates NEW Account creations on the Box side? Or does it simply send group memberships to Box and wait for Box accounts to be created either by provision or manual creation?
    Expand Post
  • j5v7c (j5v7c)

    Im stuck on this question as well.
  • r42cz (r42cz)

    When I tested this feature Okta did not initiate user account creation. I have a group being pushed containg members with and without existing Box accounts and it ignored those without accounts already.
    Selected as Best
This question is closed.
Loading
Using Group Push via SAML for BOX app configuration.