Server-side actions no longer supported in Web App Integrations

On December 1st, the options to create a preliminary callback URL or a server-side integration will no longer be available for OAuth 2.0 web app integration.

Next steps

If you have the server-side integration already configured for your applications, it will still be working. If you wish to stop using the feature or perform adjustments in your settings, see this document for workaround options and support.

For more information about web app integrations, see the documentation.

Where to get support

Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.

Box Python SDK v3.5.1 released

Bug Fixes

• Renew connection when Connection reset error occurs (#771) (bcaab27), closes #756 #757 #763 #765 #766 #770
• Retry JWT auth when got error: required unique jti claim. (#768) (878e958)
• Update pyjtw dependency to work with Python 3.10 (#772) (b13c5cd)

Box CLI v3.6.0 released

New Features and Enhancements

• Add id and type field to shared-links:create response (#427) (5ea4cb8)
• Add fields disposition_at field for files under retention (#429) (db824ef)

Bug Fixes

• Fix event:poll polling-interval (#430) (9ada74b)

Box Java SDK v3.8.0 released

New Features and Enhancements

• Added Box Sign webhooks (#1109) (99051a5)

Bug Fixes

• NullPointerException when using BoxSignRequestPrefillTag (#1121) (73fd5b6), closes #1120
• Regenerate JWT ID and retry auth request when JTI claim is rejected (#1110) (420da0f)

Dependency Upgrades

• Bumped org.bitbucket.b_c:jose4j:0.9.0 (#1111) (349694d)

Box Node SDK v2.7.2 released

Bug Fixes

• Add fields query parameter to file and folder update (#776) (a327deb)

Box iOS SDK v5.4.0 released

New Features and Enhancements

• Add content_type field to Sign Requests signer (#871) (1ec5b01)
• Add redirect_url and declined_redirect_url to Sign Request (#870) (f94d988)
• Add support for sign webhook triggers (#875) (994bfaf)
• Added method to remove retention policy assignment (#873) (c5f146c)
• Added support for Modifiable Retention Policies (#872) (e2b7a17)

Box CLI v3.5.0 released

New Features and Enhancements

• Add option to change name of downloaded file in save-asparameter (#415) (81fe64e)
• Add support for modifiable retention policies & enable deleting retention policy assignment (#420) (26ab5b4)

Box Node SDK v2.7.1 released

Bug Fixes

• Export missing RetentionType (#774) (7e6b244)

Introducing Shield Information Barrier

Shield information barrier prevents communication that could lead to conflicts of interest or potential legal issues. For example, admins can use information barrier to separate teams working on different projects to prevent collaboration on content restricted to specific groups.

Shield Information Barrier API

Shield information barrier comes along with the new API that you can use to:

• Create, manage, and list Shield information barriers
• Create, update, delete, and list Shield information barrier segments
• Create, delete, and list Shield information barrier segment restrictions
• Create, delete, and list Shield information barrier segment members
• Create and list Shield information barrier reports

Shield Information Barrier Events

Setting up the information barrier produces the following events:

• Events triggered when the user configures the information barrier, for example activates or deactivates the barrier.
• Events triggered when the user performs restricted actions, for example attempts to move an item to a restricted folder or add a user to a restricted group.

For a list of all events, see the Shield information barrier event triggers reference.

Where to get support

Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.

Box Node SDK v2.7.0 released

New Features and Enhancements

• Add support for modifiable retention policies & enable deleting retention policy assignment (#769) (5e8c776)