Known Issues for Tufts Box.net Implementation

Single Sign-On

1. You must close your browser to sever your authenticated session to Box.com, merely navigating away or logging out of Box will not sever the authenticated session.

Name Changes & Email Aliases

1. If you change your name at Tufts, thus prompting a change of your first.last@tufts.edu an administrator will need to update your account in Box in order to ensure the same permissions on the new email alias as the old email alias.
2. If you try to share to a secondary alias, it will try to create a new box account, account sharing should always go to first.last@tufts.edu, or the primary smtp alias for the user.

Personal Accounts

1. Personal accounts created with a users first.last@tufts.edu need to be administratively moved by Box.com staff in order to take advantage of the Enterprise licensing.

Box Sync

1. Some reports of the sync application for iPad not being able to open certain word docs - investigating.
2. Box Sync v4 for Windows requires .NET 3.5 and either .NET 4 or NET4.5 installed. For Windows 8, .NET 4.5 comes enabled off the box, but .NET 3.5 needs to be enabled on before the installation. To install .NET 3.5 on Windows 8 and 8.1, please reference this article 

   Box Search

1. Box search currently only supports Full text-search to the first 10000 characters of a document for performance reasons. Are the evaluation reports very long?
   • While file types pdf and csv are supported, xls is not listed as supported, but xlsd is.

File Timestamps (All Box clients Mobile, Sync, Website)

1. File timestamps (create/modify dates) are not retained when a file is uploaded to Box. They are instead replaced with the date the file was uploaded (create date) or theretofore altered (update date).
   • Box has open incidents for this functionality gap and is looking into a solution for this known deficiency.

1. Sometimes a logon to SSO box.net repeatedly prompts for username and password, even if the username and password is correct
   • This is related to Extended Protection for ADFS and will be repealed
   • Extended protection affects Firefox, Chrome and Safari browsers mostly, it is not a problem for native IE browsers
2. m.box.com does not function with SSO credentials unless you leave the password field BLANK when logging in ( this behavior will only occur during pilot phase.)
   • box.com does not function with SSO credentials unless you leave the password field BLANK when logging in ( this behavior will only occur during pilot phase.)
     • Both of these are fixed as of 10/18/2012
3. tufts.box.com/login does function with SSO credentials
4. SSO self-service provisioning is currently sending – "partner_user_id parameter should be set" Still working to resolve.
   • The iPad "Box" application from box itself does have the ability inside accounts to prompt for password persistently or force a logout which can be used to update the password.
5. The in-browser office suite editors work but they're painfully slow/clunky compared to native clients
6. user cannot create account by visiting https://tufts.box.com
   • user likely already has a personal box account with first.last@tufts.edu reserved
     • 1) box.com support can forcibly move the account to the enterprise
     • 2) user can change their first.last@tufts.edu email to an alternate address in their personal account options. They can then join tufts enterprise by loggin in using the standard join process.
7. problem with adfs http caching between office 365 and box.com currently.