Oracle9iAS Single Sign-On Application Developer's Guide Release 3.0.9 Part Number A90343-01 |
|
Oracle9iAS Single Sign-On Application Developer's Guide provides the information you need to understand and use the Oracle9iAS Single Sign-On product and its related applications
This preface contains these topics:
Application Developer's Guide is intended primarily for application developers responsible for integrating Oracle9iAS Single Sign-On with partner applications.
Application Developer's Guide is also provided for anyone who wants to understand how Oracle9iAS Single Sign-On works.
This document contains:
Chapter 1, "Introduction" explains how Oracle9iAS Single Sign-On solves the problems associated with using and administering user names and passwords for multiple applications in an enterprise.
Chapter 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 Oracle9iAS 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.
For more information, see these Oracle resources:
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 Oracle9iAS 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
This section describes the conventions used in the text and code examples of this documentation set. It describes:
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.
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.
Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|