OracleAS Single Sign-On Partner Application SDK
Copyright (c) 1999, 2003, Oracle. All rights reserved.
Contents
* Introduction
* System Requirements
* Installation and testing
Introduction
The OracleAS Single Sign-On Partner Application SDK includes
required library and PL/SQL packages. These are required for
developing and testing Oracle Single Sign-On enabled applications
using PL/SQL and Java.
System Requirements
- Oracle database (9.0.1 or higher)
- OracleAS HTTP Server
- OracleAS Single Sign-On Server
- OracleAS Single Sign-On Partner Application SDK
Installation
A) Load PL/SQL packages
i) Create a schema for Partner Application
sqlplus "sys/<sys password> as sysdba"
SQL> create user <ssosdk_schema_name> identified by <password>
SQL> grant connect, resource to <ssosdk_schema_name>
ii) Load SDK PL/SQL packages
- Go to the packages directory
- Load the PL/SQL packages using SQL Plus into the partner schema
sqlplus <ssosdk_schema_name>/<password>
SQL>@loadsdk.sql
B) Configuration for PL/SQL based application
Note: If you are not developing PL/SQL based application then
you can ignore the following section.
- Load your PL/SQL based application into the schema where you have
loaded SDK packages in step A(ii)
- Create a DAD (Database Access Descriptor) for your application
Make sure to set the authentication mode is not set to Single Sign-On.
You may set it to Basic. Provide other necessary information
such as DAD name, database information etc.
- You may use the example application that comes with this SDK.
The example files are located in the demo/plsql directory.
C) Configuration for Java Servlet/JSP based applications
Note: If you are not developing Java based application then
you can ignore the following section.
- Install the jar file into the classpath of your web server. The jar file
is located in the jlib directory. You need to make sure that
required JDBC libraries are in your web server classpath. This is
required by the java classes located in the demo/java/beans directory.
- You may use example Servlet/JSP based applications for testing.
These files are located in the demo/java directory. You need to
update corresponding Java bean with the required information regarding
where you have installed required SDK PL/SQL packages in the step A(ii).
D) Registering application with the Single Sign-On Server
Note: You need to determine the Home URL, Success URL and Logout URL for
your application before registering with SSO Server.
Use following convention for Home URL, Success URL and Logout URL:
Home URL:
---------
PL/SQL : URL for the sample_sso_papp.ssoapp procedure
Example: http://<ohs_host>:<port>/<dad_name>/<schema_name>.sample_sso_papp.ssoapp
Servlet : URL for the SSOPartnerServlet servlet
Example: http://<ohs_host>:<port>/servlet/SSOPartnerServlet
JSP : URL for the ssosignon.jsp page
Example: http://<ohs_host>:<port>/jsp/papp.jsp
Success URL:
------------
PL/SQL : URL for the sample_sso_papp.sign_on procedure
Example: http://<ohs_host>:<port>/<dad_name>/<schema_name>.sample_sso_papp.sign_on
Servlet : URL for the SSOSignOnServlet servlet
Example: http://<ohs_host>:<port>/servlet/SSOSignOnServlet
JSP : URL for the ssosignon.jsp page
Example: http://<ohs_host>:<port>/jsp/ssosignon.jsp
Logout URL:
-----------
PL/SQL : URL for the sample_sso_papp.logout procedure
Example: http://<ohs_host>:<port>/<dad_name>/<schema_name>.sample_sso_papp.sign_on
Servlet : URL for the SSOPartnerLogoutServlet servlet
Example: http://<ohs_host>:<port>/servlet/SSOPartnerLogoutServlet
JSP : URL for the papplogoff.jsp page
Example: http://<ohs_host>:<port>/jsp/papplogoff.jsp
- You need to register your application with SSO Server.
Please refer to the SSO Server Administrator's guide for details.
- Populate registration information into the SSOSDK schema that was
created in the step A(i)
sqlplus <ssosdk_schema_name>/<password>@<tnsname>
SQL>@regapp.sql
regapp.sql requires following parameters:
p_listener_token : Listener token for your application
Syntax : <partner_application_webserver_hostname>:<webserver_port>
Example : www.partner-app.com:7777
Description : This parameter is used to identify the partner application
configuration information from wwsec_enabler_config_info$
table. If port number is 80(http) or 443(https) then use
only host name as listener token i.e. www.partnerapp.com
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 SSO Server administrator
p_site_id : Site id for your application.
Description : This parameter will be supplied by the SSO Server administrator
p_login_url : Login URL of the SSO Server
Example : http://www.ssosvr.com/pls/orasso/orasso.wwsso_app_admin.ls_login
Description : This parameter will be supplied by the SSO Server administrator
p_encryption_key : Encryption key for your partner application
Description : This parameter will be supplied by the administrator
p_ip_ckeck : IP address check flag for security purpose.
Example : N
Description : Set it to Y for added security. Otherwise set it to N
E) Testing example applications
Once you have successfully completed all required installation steps, then you can
access your application using following links:
For example PL/SQL based application:
Example: http://<ohs_host>:<port>/<dad name>/<schema_name>.sample_sso_papp.ssoapp
For example Servlet based application:
Example: http://<ohs_host>:<port>/servlet/SSOPartnerServlet
For example JSP based application:
Example: http://<ohs_host>:<port>/jsp/papp.jsp
Note: Each partner application should have own SSOSDK schema.
For example, you are developing PL/SQL based application only,
then you can not test Servlet or JSP based applications.
- 1
- 2
- 3
前往页