Glossary

dads.conf

File on the Oracle HTTP server that is used to configure a database access descriptor.

database access descriptor

Database connection information for a particular OracleAS component such as the the single sign-on schema.

dynamic directive

HTTP response header that uses special error codes to enable an application to request single sign-on functionality without having to implement the single sign-on protocol.

external application

An application that does not delegate authentication to the single sign-on server. Instead, it displays an HTML login form that asks for an application user name and password. At the first login, you can choose to have the server retrieve these credentials for you. Thereafter, you are logged in to the application transparently.

forced authentication

The act of forcing you to reauthenticate if you have been idle for a preconfigured amount of time. OracleAS Single Sign-On enables you to specify a global user inactivity timeout. This feature is intended for installations that have sensitive applications.

GET

Authentication method whereby login credentials are submitted as part of the login URL.

HTTP response headers

Data embedded in a single sign-on application that instructs the mod-osso-enabled single sign-on server to perform some action such as forced authentication or single sign-off. Absent such headers, applications must use the single sign-on SDK to interact with the single sign-on system.

httpd.conf

File used to configure the Oracle HTTP Server.

mod_oc4j

Oracle HTTP module that communicates Web requests to the OC4J engine.

mod_osso

Module on the Oracle HTTP server that enables applications protected by OracleAS Single Sign-On to accept HTTP headers in lieu of a user name and password once the user has logged into the single sign-on server. The values for these headers are stored in the mod_osso cookie.

mod_osso cookie

User data stored on the HTTP server. The cookie is created when a user authenticates. When the same user requests another application. The Web server uses the information in the mod_osso cookie, not the single sign-on cookie, to log the user in to the application. This feature speeds server response time.

OC4J (Oracle Containers for J2EE)

A lightweight, scalable container for Java2 Enterprise Edition.

Oracle HTTP Server

Software that processes Web transactions that use the Hypertext Transfer Protocol. Oracle uses HTTP software developed by the Apache Group.

partner application

An application that delegates the authentication function to the single sign-on server. This type of application spares you from reauthenticating by accepting mod_osso headers or by redirecting you to the server itself. To redirect users itself, the application must be integrated with the single sign-on SDK.

POST

Authentication method whereby login credentials are submitted within the body of the login form.

single sign-off

Process by which you terminate a single sign-on session and log out of all active partner applications simultaneously. You do this by logging out of the application you are working in.

single sign-on SDK

The APIs that enable partner applications for single sign-on. The SDK consists of PL/SQL and Java APIs as well as sample code that demonstrates how these APIs are implemented.

single sign-on server

Program logic that enables you to log in securely to single sign-on applications such as expense reports, mail, and benefits.