Box Provisioning Guide


The Okta integration with Box enables organizations to use Single Sign On (SSOAn acronym for single sign-on. In a SSO system, a user logs in once to the system and can access multiple systems without being prompted to sign in for each one. Okta is a cloud-based SSO platform that allows users to enter one name and password to access multiple applications. Users can access all of their web applications, both behind the firewall and in the cloud, with a single sign in. Okta provides a seamless experience across PCs, laptops, tablets, and smartphones.), Okta ProvisioningProvisioning is the enterprise-wide configuration, deployment, and management of multiple types of IT system resources. Specifically, provisioning provides users access to equipment, software, or services. This involves creating, maintaining and deactivating required business process automation objects and attributes in systems, directories, and applications., or SSO + Okta Provisioning.

Purpose of the guide

The Okta + Box Provisioning Guide describes how to configure Okta Provisioning for Box. It also describes alternative configuration options, including customizing attributes and managing user groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups.. Troubleshooting tips are also provided.

About Okta Provisioning

Okta Lifecycle Management (LCM) is a product with multiple functions. These include imports, access-request workflow, groups, group rules, and provisioning to and from applications (cloud-based and on-premises). The latter of these—Okta Provisioning, is foundational to LCM.

Okta Provisioning is a workflow comprised of various functions. These functions are best described by the CRUDReferencing the common database operations of Create, Read, Update, and Deactivate (instead of Delete). The CRUD principle is used in Okta for the management of users in the Okta Universal Directory. principle—the common database operations of Create, Read, Update, and Deprovision (instead of Delete) users.

When events occur that impact a user's lifecycle, such as an employee position change, appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. license expiration, and employment termination, Okta Provisioning functions are triggered that can then change the user's lifecycle state.

See the Okta Lifecycle Management User Provisioning User Guide.

Supported features

The Okta integration with Box supports the following:

  • Push groups

    Groups and their members can be pushed to integrated applications.

  • Import new users

    Users created in a third-party application can be pulled into Okta.

  • Import profile updates

    Updates made to a user profile in Box are pulled into the counterpart user profile in Okta.

  • Push new users

    Users created in Okta are pushed to Box.

  • Push profile updates

    Changes made to a user profile in Okta are pushed to Box.

  • Push user deactivation

    Deactivating a user in Okta deactivates the user account in Box.

  • Reactivate users

    User accounts can be reactivated in Box.

What's covered in the guide