Locating Access SDK Packages and Resources

2-4 Developers Guide for Oracle Access Manager and Oracle Security Token Service of HTTP cookies are outside of the scope of Access SDK. You can develop Access Clients to protect non-HTTP resources as easily as agents protecting HTTP resources. The typical functions that a custom Access Client can perform, individually or in combination with other Access Clients, are as follows: ■ Authenticate users by validating their credentials against Oracle Access Manager and its configured user repositories. ■ Authenticate users and check for authorization to access a resource. ■ Authenticate users and create unique Oracle Access Manager sessions represented by session tokens. ■ Validate session tokens presented by users, and authorize their access to protected resources. ■ Terminate Oracle Access Manager sessions given a session token or a named session identifier. ■ Enumerate Oracle Access Manager sessions of a given user by specifying named user identifier. ■ Save or retrieve custom Oracle Access Manager session attributes. Some Access Client operations are restricted for use by the designated Access Client instances. For example, see OperationNotPermitted in Oracle Access Manager Access SDK Java API Reference. An Oracle Access Manager administrator can use the Oracle Access Manager administration console to control the privileges of individual Access Clients. For more information, see Oracle Fusion Middleware Administrators Guide for Oracle Access Manager with Oracle Security Token Service.

2.4 Messages, Exceptions and Logging

This section describes the messages and exceptions used by the Access SDK to indicate status or errors. The execution log generated by the Access SDK is also described. The execution log provides information about operations performed. For example, operation status, any errors or exceptions that occur, and any general information that is helpful for troubleshooting. The following topics are discussed in this section: ■ Messages ■ Exceptions ■ Logging

2.4.1 Messages

The Access SDK provides support for localized messages that indicate status or error conditions. Error messages, which are provided to the application as exceptions, are also localized. These localized error messages are logged in the Access SDK log file.

2.4.2 Exceptions

The following types of exceptions are used to indicate error conditions to an application: