
 Oracle Web Single Sign-On
 Partner Application SDK version: 3.0.7
 Copyright (c) 2001 Oracle Corporation. All rights Reserved.
==================================================================

What you need to start writing a Single Sign-On enabled 
Partner Application

 1. Oracle database 8.1.6+ with Java option
 2. Oracle iAS webserver
 3. Oracle Single Sign-On server
 4. Oracle Single Sign-On Partner Application SDK

Installation Steps:

Note:
    For Servlet or Java Server Page application development, the 
    Java SDK jar file must be there in the classpath of webserver. 
    This jar file is in jlib directory. 
    All Java bean class files must be in the web server classpath

A) If you are using Oracle 8i Release 2(8.1.6)
   then follow this steps. 
   If you are using  Oracle 8i Release 3(8.1.7) or above then go 
   to step B

   PL/SQL crypto packages 
   Go to $ORACLE_HOME/rdbms/admin 
   SQLPLUS> connect sys/<password> as sysdba 
   SQLPLUS> @catobtk.sql 
   SQLPLUS> @catoctk.sql 
   SQLPLUS> grant execute on dbms_obfuscation_toolkit to public;
   SQLPLUS> grant execute on dbms_crypto_toolkit to public;

B) Load OWA packages
   If you have iAS installed then, you can find OWA packages in the
   following default directory:
        $ORACLE_HOME/Apache/modplsql/owa
   You need to run owaload.sql to load owa packages.
   Please read that file for more information

   SQLPLUS> conenct sys/<password>@<tnsname> as sysdba
   SQLPLUS> @owaload.sql <log_file_name> 

C) Create a schema for partner application

   SQLPLUS> connect sys/<password>@<tnsname> as sysdba 
   SQLPLUS> create user <schema_name> identified by <schema_password>
   SQLPLUS> grant connect, resource  to <schema_name>

   Load packages for partner application. 
   Go to the packages directory 

   1.Run the following command 
     go to packages/oracle/security/sso
     loadjava -user <partner_schema_name>/<password>@<tnsname> SSOHash.class

   2. Load the plsql packages from SQL Plus to the partner schema
     SQLPLUS>@loadsdk.sql 
     It will generate loadsdk.lst and on.lst spool file

   3. Get partner registration information from SSO server administrator
      If you are the administrator of the Login Server then follow these
      steps for adding your partner application to the Login Server
   
      a) Login to Portal with  SSO administrator privilege
         (example: portal30_sso/<password>)
         - Click on  Administrator tab
         - Click on Services->Login Server Administation link
         - Click on Administrator Partner Application
         - Click on Add Partner Application
      b) Enter your application name 
           Example: Sample Partner Application 3.0.7
      c) Enter home url for your application
           This url should be accessible publicly which don't require any
           authentication. This is url will be listed in the Login Server
           homepage.
           Example: http://www.<your_webserver_name.domain>
      d) Enter success url for your partner application
           This url will be implemented by your. 
         Example:
           PL/SQL :
               http://www.<your_webserver_name.domain>/pls/<sample_dad>/<partner_application_schema_name>.sample_sso_papp.sign_on
           Servlet:  
               http://www.<your_webserver_name.domain>/servlet/SSOSignOnServlet
           JSP: 
               http://www.<your_webserver_name.domain>/jsp/ssosignon.jsp 
     
       e) You may enter the start and end date or leave as it is 
       f) Enter your Partner Application administrator name and email.
      
      Now click on Apply button. Login Server will display the registration
      information for Partner Application.
      You should note down the following information for step 4.
        ID, Token, Encryption Key
  
   4. Edit regapp.sql file and update all necessary information

      NOTE: If you have already registered your application to the Login 
       Server in step 3, still you need to follow this step. This step
       will store Login Server registration information in Partner 
       Application configuration table
     
      SQLPLUS> connect <partner_schema_name>/<password>@<tnsname>
      SQLPLUS>@regapp.sql 

      regapp.sql needs contains following paramaters:

        p_listener_token : Listener token for your application
          Syntax         : <application name>:<SSO webserver host name>:<port> 
          Example        : fooapp1:www.ssosvr.com:80
          Description    : This parameter is used to identify an Partner Application
                           from configuration information. This name will be used
                           inside the sample application code. 
                    
        p_site_token     : Site token for your application.
          Description    : This parameter will be supplied by the administrator 

        p_site_id        : Site id for your application. 
          Description    : This parameter will be supplied by the administrator

        p_login_url      : Login url of Login Server 
          Example        : http://www.ssosvr.com/pls/portal30_sso/portal30_sso.wwsso_app_admin.ls_login
          Description    : If you don't know the Login url then you can click 
                           on login link in the Portal. Portal it will display the 
                           Login page. Copy the link from your browser window and 
                           use it as your Login Server login url

        p_cookie_version : Version of the SSO server cookie
          Example        : v1.0
          Description    : The cookie version for this version of SDK will be v1.0

        p_encryption_key : Encryption key for your application
          Description    : This parameter will be supplied by the administrator
     
        p_ip_ckeck       : IP address check flag for security purpose.
          Example        : Y
          Description    : Set it to Y for added security. Otherwise set it to N


