Documentation
Introduction

Use this guide to enable Service Provider (SP)-initiated 2-Factor Authentication and Single Sign-on (SSO) access via SAML to Box.

For SecureAuth IdP-initiated access, refer to Box (IdP-initiated) Integration Guide

Prerequisites

1. Have an enterprise tier Box account

SSO is available for only this pricing tier

2. Ensure that SAML SSO is enabled through an administrator account

Submit a support ticket to Box to enable SSO, and allow 2-3 days for processing before it is available

3. Acquire the Box SAML documentation that will provide necessary URLs for the SecureAuth IdP configuration

See Single Sign On (SSO) with Box: For Administrators at the Box Community website for assistance

Consult a Box engineer to configure SP-initiated by Post Authentication

This requires the SAML Consumer URL – e.g. https://sso.services.box.net/sp/ACS.saml2

and may require the direct SP Start URL – e.g. https://sso.services.box.net/sp/startSSO.ping?PartnerIdpId=https://example.com/secureauth[realm#]&TargetResource=#target_resource#

4. Create a New Realm for the Box integration

5. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined
  • Data – an enterprise directory must be integrated with SecureAuth IdP
  • Workflow – the way in which users will access this application must be defined
  • Registration Methods – the 2-Factor Authentication methods that will be used to access this page (if any) must be defined
SecureAuth IdP Configuration Steps
Data

 

1. In the Profile Fields section, map the directory field that contains the user's Box ID to the SecureAuth IdP Property

For example, add the Box ID to the Email 2 Property if it is not already contained somewhere else

Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Workflow

 

2. In the SAML 2.0 Service Provider section, provide the SP Start URL to enable SSO and to redirect users appropriately to access Box

In this example, the direct SP Start URL is https://sso.services.box.net/sp/startSSO.ping?PartnerIdpId=https://example.com/secureauth19&TargetResource=#target_resource#

Click Save once the configurations have been completed and before leaving the Workflow page to avoid losing changes

Post Authentication

 

3. Select SAML 2.0 (SP Initiated) Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin

4. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/SAML20SPInit.aspx)

5. A customized post authentication page can be uploaded, but it is not required

User ID Mapping

 

6. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Box ID (Email 2)

7. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if Box requires it, which the SP will provide

8. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation

 

9. Set the SAML Consumer URL – e.g. https://sso.services.box.net/sp/ACS.saml2

10. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Box

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Box side

11. Set the SAML Audience to the URL provided by the Box SAML documentation

In typical Box deployments, the URL is https://sso.services.box.net/sp/ACS.saml2, but refer to the documentation for confirmation

12. Set the SAML Offset Minutes to make up for time differences between devices

13. Set the SAML Valid Hours to limit for how long the SAML assertion is valid

No configuration is required for the WSFed Reply To/SAML Target URL, or SAML Recipient fields

14. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, click Select Certificate and choose the appropriate certificate

15. Provide the Domain in order to Download the Metadata File to send to Box

This will assist Box in enabling SSO

SAML Attributes / WS Federation

 

16. Enter the required SAML Attributes, providing the Name and selecting the Value from the dropdown for each Attribute

In this example Attribute 1 is configured for Email 2, Attribute 2 is configured for First Name, and Attribute 3 is configured for Last Name

Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

 

17. Click View and Configure FormsAuth keys / SSO token to configure the token/cookie settings and to configure this realm for SSO

These are optional configurations

 To configure this realm's token/cookie settings, follow these steps:
Forms Authentication


1. If SSL is required to view the token, select True from the Require SSL dropdown

2. Choose whether SecureAuth IdP will deliver the token in a cookie to the user's browser or device:

  • UseCookies enables SecureAuth IdP to always deliver a cookie
  • UseUri disables SecureAuth IdP to deliver a cookie, and instead deliver the token in a query string
  • AutoDetect enables SecureAuth IdP to deliver a cookie if the user's settings allow it
  • UseDeviceProfile enables SecureAuth IdP to deliver a cookie if the browser's settings allow it, no matter the user's settings

3. Set the Sliding Expiration to True if the cookie remains valid as long as the user is interacting with the page

4. Set the Timeout length to determine for how many minutes a cookie is valid

No configuration is required for the Name, Login URL, or Domain fields

Machine Key

5. No changes are required in the Validation field, unless the default value does not match the company's requirement

If a different value is required, select it from the dropdown

6. No changes are required in the Decryption field, unless the default value does not match the company's requirement

If a different value is required, select it from the dropdown

No configuration is required for the Validation Key or Decryption Key fields

Authentication Cookies

 

7. Enable the cookie to be Persistent by selecting True - Expires after Timeout from the dropdown

Selecting False - Session Cookie enables the cookie to be valid as long as the session is open, and will expire once the browser is closed or the session expires

No configuration is required for the Pre-Auth Cookie, Post-Auth Cookie, or the Clean Up Pre-Auth Cookie fields

Click Save once the configurations have been completed and before leaving the Forms Auth / SSO Token page to avoid losing changes

To configure this realm for SSO, refer to SecureAuth IdP Single Sign-on Configuration

To configure this realm for Windows Desktop SSO, refer to Windows Desktop SSO Configuration Guide