Knowledge Base

Support Policies

Box (SP-Initiated) Integration Common Configuration Issues

SecureAuth IdP Version affected: All

 

Description:

Box (SP-Initiated) Integration has changed due to the Box changing their requirements and configurations over time. This has been confirmed over the phone with Box engineers setting up the integration. This is just to expand on the knowledge that is currently provided in the following document.

https://docs.secureauth.com/display/90docs/Box+%28SP-initiated%29+Integration+Guide

 

Resolution:

The following may also need to be completed in order to successfully complete a Box integration.

1. Post Authentication cannot be SP initiated by Post and cannot be configured as SP initiated by Post on Box's side either. You may need to speak with a Box engineer to configure this.

2. Post Authentication must contain Consumer URL: (ex: https://sso.services.box.net/sp/ACS.saml2)

3. Post Authentication may need the direct SP Start URL (ex: https://sso.services.box.net/sp/startSSO.ping?PartnerIdpId=https://example.com/secureauth19&TargetResource=#target_resource#)

Box_Integration_1.PNG

 

4. SAML Attributes that may be required: Email, FirstName, LastName

Box_Integration_2.PNG

 

Congratulations! You have configured for Box (SP-Initiated) Integration!

If you were not successful, the admin console for Box may no longer be configurable without a Box engineer, so you may need one on the line to complete the integration. SecureAuth and Box are currently working on updating documentation for integration between the two.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.