Known Issues for Tufts Box.net Implementation

Open Issues

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.

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.

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
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
tufts.box.com/login does function with SSO credentials
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.

The in-browser office suite editors work but they're painfully slow/clunky compared to native clients

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.