Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You are redirected to a logon page or an error page, or you are prompted for authentication information when you click a hyperlink to a SSO Web site in an Office document
Article ID: 899927 - View products that this article applies to.
When you click a hyperlink in a Microsoft Office document, you may experience the following behavior before you can open the page that you requested:
Office lets you edit and author documents on a Web site if the server supports Web authoring and collaboration. First, Office tries to communicate with the Web server. Then Office tries to directly bind to the resource by using the Microsoft Hyperlink Library (Hlink.dll) and the URLMON API. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
838028When Office sends the Web page request, you may be redirected to the Web site logon page for the SSO system. This behavior occurs because the Office session is independent of the Web browser session in which you may have already provided user credentials.
(http://support.microsoft.com/kb/838028/ )How documents are opened from a Web site in Office 2003
Because the sessions are independent, session cookies are not shared. If the SSO system exclusively relies on session cookie information, the SSO system may not appear to work because the same user moves from more than one session. This behavior is a fundamental design limitation of an SSO system when the SSO system is not designed to support SSO authentication across more than one browser or Web-aware application on the client desktop. Because Office is a fully Web-aware application, the issue may appear unique to Office applications if they are the only Web-aware clients that are installed by the client. However, the root cause of this issue is not limited to Microsoft Office, and this problem may occur when you use third-party software.
The problem is a limitation of the SSO system that is used by the Web server. However, you may be able to reduce the current effects for your SSO-protected Web site by using one of the following methods.
Hyperlinks from Internet Explorer to OfficeIf this issue occurs when hyperlinks on a Web page open an Office file and the Web page is hosted in Internet Explorer, you can avoid this issue by explicitly marking the content as a read-only download instead of as an inline navigation.
To do this, add a custom HTTP header to the GET response for the Office file contents. Add the "Content-Disposition: Attachment" header. When a GET response contains this header, Internet Explorer prompts the user to open or save the download. If the user chooses to open the download, the file opens from the Internet Explorer Temporary File cache read-only. The user may choose to modify and save the file locally. However, the user will not be able to save the file to the server or collaborate with Web services for the Web site. Therefore, this solution only works if you intend to make the file read-only.
You can set the "Content-Disposition" header by using code in Microsoft Active Server Pages (ASP), in Microsoft ASP.NET, or in ISAPI when you work with dynamically generated content. If the content is static, you can configure the header for a given file or folder by using IIS Manager and the IIS metabase. For more information about the Content-Disposition HTTP header, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260519/ )How to raise a "File Download" dialog box for a known MIME type
Hyperlinks from Office to Internet Explorer or to another Web browserIf this issue occurs when you click hyperlinks in Office documents that either directly open HTML Web content or are redirected to HTML content, client users can avoid the problem by enabling a registry key to send the hyperlink navigation to the browser instead of directly binding to the hyperlink from Office. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
218153Note Regardless of the version of Office that you have installed, add the registry key in the exact location that is specified in Microsoft Knowledge Base article 218153.
(http://support.microsoft.com/kb/218153/ )Error message: "Cannot locate the Internet server or proxy server" when clicking hyperlink
When you use this registry setting, the HLINK component that is used by Office opens the hyperlink in the default Web browser. This registry setting affects all HLINK clients, not just Office. Therefore, use this registry key carefully. For more information about issues that may occur if you use this workaround, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/280680/ )Cannot follow hyperlink to Office document
To fully resolve this issue, we encourage SSO providers to develop a system that could allow for Web authoring and a client that uses multiple sessions. This configuration adds complexity to the SSO system. However, this configuration also offers clients the most usability options. Microsoft is currently working with key SSO providers for a long-term solution.
Additionally, Microsoft is investigating how end users use Office to better predict and manage the following scenarios:
If you are an SSO designer or developer, you can add support for multiple-session clients. For example, you may use the following methods:
Article ID: 899927 - Last Review: May 13, 2007 - Revision: 4.1