Oracle Single Sign-On Application Developer's Guide
Release 3.0.6

Part Number A86782-03

Library

Service

Index

Go to previous page Go to next page


Preface

Oracle Single Sign-On Application Developer's Guide provides the information you need to understand and use the Single Sign-On product and its related applications.

This preface contains these topics:

Audience

Oracle Single Sign-On Application Developer's Guide is intended primarily for application developers responsible for integrating Single Sign-On with partner applications.

Oracle Single Sign-On Application Developer's Guide is also provided for anyone who wants to understand how Single Sign-On works.

Organization

This document contains:

Chapter 1, "Introduction" explains how Single Sign-On solves the problems associated with using and administering user names and passwords for multiple applications in an enterprise.

Table 2, "Concepts and Architecture" discusses the significance of Single Sign-On to users and administrators in an enterprise. It describes the components of Single Sign-On, the application types, and the authentication methods Single Sign-On uses. It also explains the process and architecture through which Single Sign-On authenticates users to applications.

Chapter 3, "PL/SQL Single Sign-On Application Programming Interface" explains how to use the PL/SQL Single Sign-On Application Programming Interface (API).

Chapter 4, "Java Oracle Single Sign-On Application Programming Interface" explains how to use the Java Single Sign-On Application Programming Interface.

Chapter 5, "Examples in PL/SQL and Java" explains how to install Application Programming Interfaces for PL/SQL and Java and gives examples of installation code.

Related Documentation

For more information about development related issues, refer to the Readme file included in the Software Development Kit (SDK).

For additional information, see the online help and related documentation for Oracle Portal.

In North America, printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

http://www.oraclebookshop.com/

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://technet.oracle.com/membership/index.htm

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://technet.oracle.com/docs/index.htm

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention  Meaning  Example 

Bold 

Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both. 

The C datatypes such as ub4, sword, or OCINumber are valid.

When you specify this clause, you create an index-organized table.  

Italics 

Italic typeface indicates book titles, emphasis, syntax clauses, or placeholders. 

Oracle8i Concepts

You can specify the parallel_clause.

Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading. 

UPPERCASE monospace (fixed-width font) 

Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, user names, and roles. 

You can specify this clause only for a NUMBER column.

You can back up the database using the BACKUP command.

Query the TABLE_NAME column in the USER_TABLES data dictionary view.

Specify the ROLLBACK_SEGMENTS parameter.

Use the DBMS_STATS.GENERATE_STATS procedure. 

lowercase monospace (fixed-width font) 

Lowercase monospace typeface indicates executables and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, user names and roles, program units, and parameter values. 

Enter sqlplus to open SQL*Plus.

The department_id, department_name, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect as oe user. 

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention  Meaning  Example 

[ ] 

Brackets enclose one or more optional items. Do not enter the brackets. 

DECIMAL (digits [ , precision ]) 

{ } 

Braces enclose two or more items, one of which is required. Do not enter the braces. 

{ENABLE | DISABLE} 

A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar. 

{ENABLE | DISABLE}

[COMPRESS | NOCOMPRESS] 

... 

Horizontal ellipsis points indicate either:

  • That we have omitted parts of the code that are not directly related to the example

  • That you can repeat a portion of the code

 

CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM employees; 

.

.

. 

Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. 

 

Other notation 

You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as it is shown. 

acctbal NUMBER(11,2);

acct CONSTANT NUMBER(4) := 3; 

Italics 

Italicized text indicates variables for which you must supply particular values. 

CONNECT SYSTEM/system_password 

UPPERCASE 

Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase. 

SELECT last_name, employee_id FROM employees;

SELECT * FROM USER_TABLES;

DROP TABLE hr.employees; 

lowercase 

Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. 

SELECT last_name, employee_id FROM employees;

sqlplus hr/hr 


Go to previous page Go to next page
Oracle
Copyright © 1996-2000 Oracle Corporation.

All Rights Reserved.

Library

Service

Index