Browser-Related Problems

Artículo
06/29/2006

Microsoft® .NET Passport services are designed to achieve the correct results for all of the most common browsers in use today.

Secure and nonsecure mode dialog boxes

Many browsers have a default setting to warn users if they are changing between secure and nonsecure modes. This setting may display up to two dialog boxes during the sign-in process: the first indicates a switch to an SSL connection and the second indicates a switch back to a non-SSL connection. In the dialog box, selecting the In the future, do not show this warning check box can turn off these messages. This is a browser behavior and cannot be defeated by .NET Passport or any other code. Microsoft .NET Passport Web sites must inform users that this dialog box may appear, depending on their browsers and security settings. A similar dialog box can be configured to appear whenever cookies are written to the client.

Mixed secure and nonsecure content dialog boxes

Microsoft .NET Passport-enabled pages can potentially serve both HTTPS and HTTP content within the same page, but will do so only if there is some error in either cobranding or LogoTag2 method calls that causes this situation. Some browsers display a warning dialog box in this situation, depending on security settings. If you are serving HTTPS pages and using the LogoTag2 method of the Passport Manager object, make sure to set the bSecure parameter to True to serve the Sign-in/Sign-out image links from a .NET Passport HTTPS image server. Also check your cobranding elements, including elements called as images and the cascading style sheet or cobranding template files.

Certificate dialog boxes from browser

The first time a .NET Passport user connects to a .NET Passport Secure Sockets Layer (SSL) page, the browser may display an acceptance dialog box for the security certificate. This is required for SSL-served pages. Users must accept this certificate to continue. During the sign-in process at the .NET Passport Login server, there is also another SSL connection that writes the "ticket-granting" cookie. It also requires the acceptance of a certificate. Your own SSL-served pages may require yet another certificate-acceptance step. After certificates have been accepted by a client browser user, the dialog box will not appear again unless the certificates expire or are specifically revoked by the certificate-issuing agency.

One customer's profile is apparently viewable by another customer, or other private data is somehow exposed to the wrong user

This is probably a proxy problem, not a .NET Passport problem, and may occur if two users within the same proxy view pages that contain .NET Passport or other private data without the server correctly causing the content to expire or qualifying the Cache-control or Pragma: no-cache directives sent to a proxy server in the header. For information about how to fix this problem, see Collecting User Data Example.

Netscape Navigator browsers display a "404 Page Not Found" error when redirected to the .NET Passport network pages

If your site is experiencing this problem with the Netscape Navigator browsers only, it is probably the result of a misplaced or missing cobranding cascading style sheet, cobranding template, or an element called by your cobranding. Make sure that a cascading style sheet is available using the path and file name you supplied for the CoBrandCSSURL and that the cobranding template is available from the URL you supplied for CoBrandURL at site registration time.

Older Navigator browsers and HTTP proxy tunneling

Some versions of Netscape Navigator have an issue that causes cross-site sign-in or registration posts to fail when certain proxies are used. The problem occurs while accessing secure and nonsecure pages in succession. In the case of a sign-in, a re-sign-in form appears. With the second or third attempt, the POST operation will succeed.

In Microsoft® Windows NT®, Navigator 4.0 fails from non-SSL to SSL and from SSL to SSL. Version 4.04 and later browsers do not have this problem.
In Microsoft® Windows® 95 or Windows 98, Navigator 3.04 fails from non-SSL to SSL and from SSL to SSL. Version 4.0 and later browsers do not have this problem.

Return URL works on Internet Explorer, but breaks on Netscape (gives 404 or other error)

Netscape browsers are less tolerant of malformed URLs. For example, a backslash ("\") in a return URL is much more likely to generate an error for a Netscape client user than an Internet Explorer client user. Special characters or spaces introduced into a URL, such as an improperly encoded returnURL or coBrandArgs parameter sent to a Passport Manager method, are also areas where many browsers will fail when handling a URL. Check the actual URL output by AuthURL2 and LogoTag2 methods of the Passport Manager and make sure that it is well-formed.

Internet Explorer 4.0 occasionally fails to connect to a Passport Manager page served using SSL

Internet Explorer 4.0 and possibly other browsers occasionally fail to handle SSL output if buffering is not enabled on the server. To work around this issue, just add "Response.Buffer=True" to the top of all SSL-served pages, or turn buffering on for the entire site.

Compartir a través de