Nov 4, 16:58 UTC
Resolved - November 4th, 2013; 11:56am ET - After extensive testing, we do believe that the previously reported authentication issues have been resolved. If you were experiencing these issues, please attempt to authenticate into your tools again. If any other issues arise, please contact our dedicated support team at support@sharefile.com, or by phone at 1-800-441-3453.
Nov 4, 16:34 UTC
Monitoring - November 4th, 2013; 11:33am ET - Engineering has released a fix to our application that should resolve the issues that were previously reported with Single Sign-On log in's to our tools. We ask that users who were previously experiencing issues please try to authenticate again. These issues should be resolved, but continued tests are being run to ensure the problem has been completely addressed.
Nov 4, 16:31 UTC
Identified - November 4th, 2013; 11:31am ET - Our engineering team has determined the cause of the previously reported authentication issues and is currently working to deploy a fix to our system that should resolve the issue. As soon as we have deployed the fix, we will provide an additional update.
Nov 4, 15:46 UTC
Update - November 4th, 2013; 10:45am ET - Our engineers are continuing to look into the issue that is impacting accounts using Single Sign-On and not allowing users to authenticate into their ShareFile tools. We will continue to provide updates as soon as they become available.
Nov 4, 14:53 UTC
Update - November 4th, 2013; 9:51am ET - Research continues on the authentication issues that are occurring for clients using Single Sign-On. These issues may be impacting other ShareFile clients such as the Outlook Plugin and mobile tools as well. Our development team continues to research the source of the issue and work towards resolution. We will provide an update as soon as possible.
Nov 4, 14:22 UTC
Investigating - November 4th, 2013; 9:19am ET - We have received reports of some accounts not being able to login to their ShareFile Sync tool when using Single Sign-On credentials. Our engineers are looking into this problem and we will provide an update as soon as possible.