
 Oracle Web Single Sign-On
 Partner Application SDK
 Login Server Compatibility: 3.0.6, 3.0.7, 3.0.8
 Copyright (c) 1999-2001 Oracle Corporation. All rights Reserved.
==================================================================

This readme file is for the Oracle Web Single Sign-On 
Partner Application SDK (SSO SDK).

The SSO SDK can be used to develop single sign-on enabled
Web applications using PL/SQL, Java Servlet, or Java Server Pages.

The SSO SDK includes reference information for implementing SSO 
partner applications in PL/SQL, Java Servlet, or Java Server Pages.

For updated versions of the SSO SDK software and documentation, go to:
http://technet.oracle.com

Frequently Asked Questions:
------------------------------------------------------------------

Q:  How do I install the SSO SDK?
A:  See the Install.txt file in this directory.

Q:  How can I develop a partner application using PL/SQL?
A:  See the ReadMe.txt file in the demo/plsql directory.

Q:  How can I develop a partner application using Java Servlet?
A:  See the ReadMe.txt file in the demo/java/servlet directory.

Q:  How can I develop a partner application using Java Server Pages?
A:  See the ReadMe.txt in the demo/java/jsp directory.

Q:  Where can I get information about SSO Java beans?
A:  See the ReadMe.txt file in the demo/java/beans directory.

Q:  I have completed the SSO SDK installation. How do I register
    my partner application to the Login Server?
A:  Decide upon a publicly visible value for the home URL for your application,
    as well as a value for the sign-on success URL, which must be able to
    receive tokens from the Login Server after users authenticate. Send the
    URL information to the Login Server Administrator, who will provide
    registration information that can be used by the partner application.

Q:  Why do I receive a PL/SQL error when I try to use my application?
A:  Your registration information is probably not set correctly in the
    configuration table. This can also occur if the listener token name is
    not correct.

Q:  How can I see the error log for debugging?
A:  Use SQL*Plus to view the error log as follows:
      SQLPLUS> connect <schema_name>/<password>@<tnsname>
      SQLPLUS> @secedbg.sql
      SQLPLUS> select * from wwsec_sso_log$;

    NOTE: When you are finished debugging, load the secnodbg.sql
    file to stop logging debug information.

Q:  What kind of web server is supported?
A:  The Oracle9i Application Server is required for developing PL/SQL based
    applications. If you are developing applications using Java Servlet
    or Java Server Pages, you can use other web servers, but you must use
    OWA packages.  OWA packages are shipped with the Oracle9i Application
    Server by default.

Q:  Why am I receiving the following error?
    WPG_SESSION api failed for pl/sql based application.
A:  Do not set the authentication mode for your application DAD 
    (Database Access Descriptor) to Single Sign-On. For example, you can 
    set it to Basic.

Q:  Why, when I try to access the partner application, does it redirect me to
    the login form of the Login Server, and then loop between the sign-on
    URL and the requested URL?
A:  Check the application cookie domain to see if the domain name/fully
    qualified host name is correct.

    For example, for .us.foo.com, you include a dot (.) before cookie domain
    name. For www.foo.com, you do not include a dot before the hostname.

    If the cookie domain name is not correct, the application cookie
    will not be set or retrieved properly.
