OSE Specification Violation During Login on Netscape V4 Browsers

Technote (FAQ)
Problem
You are logging into a secured WebSphere® Application Server resource. On several releases of Netscape V4, the login fails with an "OSE specification violation" error. However, the error does not occur in Netscape V6.0 or Microsoft® Internet Explorer.
Solution
Symptom:

You are receiving the following error when trying to login to a secured WebSphere Application Server resource:

OSE specification violation!!! ns_prepare_for_write() was already called

The error occurs on several releases of Netscape V4, but does not occur with Microsoft® Internet Explorer or Netscape V6.0.

Cause:

A plugin trace shows that several releases of Netscape V4 are not returning the token as expected. This is occurring because the single signon (SSO) and the SSO domain are set using the server name instead of just the domain name. Although domain name is usually set in the administrative console, the setting can be seen in the xmlconfig export file.

<sso-enabled ssl-enabled="false">
<domain-name>
serverName.company.com</domain-name>
</sso-enabled>

Solution:

Change your SSO domain to include just the domain name, and remove the server name:

<sso-enabled ssl-enabled="false">
<domain-name>company.com</domain-name>
</sso-enabled>












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting)
Operating system(s): Multi-Platform
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Standard, Advanced
Reference #: 1030970
IBM Group: Software Group
Modified date: 2003-12-04