Article ID: 2498069 - View products that this article applies to.
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect the computer.
You have Microsoft Office for Mac 2011 applications installed on a client computer. From that client computer, you try to access a Microsoft Office file that is stored on a Web server (such as a SharePoint server) that is configured for Basic authentication. The connection between your computer and the Web server does not use Secure Sockets Layer (SSL). When you try to open or download the file, you experience the following symptoms:
To resolve this problem, enable SSL encryption on the Web server. By default, Office for Mac 2011 applications can access and download files from a Web server that uses Basic authentication over an SSL connection.
Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
To work around this problem, let Office for Mac 2011 applications connect to a Web server by using Basic authentication over a non-SSL connection.
Caution Enabling Basic authentication without SSL can be a significant security risk.The following information describes how to enable Office for Mac 2011 applications to open Microsoft Office file types directly from a server that supports only Basic authentication over a non-SSL connection. This method should be used only if you are confident that you are using an encrypted channel between the user and the Web server. A direct cable connection or a dedicated line would be considered optimal for secure connections.
Because user credentials are not encrypted for network transmission and are sent over the network in plain text, we do not recommend that you use Basic authentication over an unsecured HTTP connection. For more information, see the More Information" section. If you want to use Basic authentication, we recommend that you always enable SSL encryption on the server.
On the client computer, add the basicauthlevel registry key and the appropriate valueImportant This section, method, or task contains steps that tell you how to change the registry. However, serious problems might occur if you change the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you change it. Then, you can restore the registry if a problem occurs.
Basic authentication is a widely used, industry-standard method for collecting user name and password information. The advantage of Basic authentication is that it is part of the HTTP specification and is supported by most browsers. However, Basic authentication prompts the user for a user name and a password. This information is then sent not encrypted over the network. The Basic authentication method is not recommended unless you are sure that the connection between the user and the Web server is secured (such as by using SSL or a direct connection). With Basic authentication, the password is sent over the network in plain text. If this password is intercepted over the network by a network sniffer, an unauthorized user can determine the user name and the password and then reuse these credentials. Because of this security risk, Basic authentication over a non-SSL connection is disabled by default for Microsoft Office applications.
Article ID: 2498069 - Last Review: August 29, 2011 - Revision: 1.1