Search Results audit_user

Overview

FND_SIGNON is the core Oracle E-Business Suite authentication and session-establishment package, owned by the APPS schema. It governs the entire sign-on lifecycle: validating a user's credentials, recording successful and unsuccessful login attempts, creating and terminating application sessions, and maintaining the navigator (menu) state associated with each responsibility. The package is a foundational security component, sitting beneath several higher-level security layers. The documented dependency listing confirms that FND_SIGNON is referenced by APPLSYSPUB, FND_SESSION_MANAGEMENT, FND_SSO_MANAGER, FND_WEB_SEC, ICX_SEC, ORACLESSWA, PON_USER_PROFILE_PKG, and PSP_SUM_TRANS, and it is classified as OTHER in the ETRM API classification. Its status is VALID in the APPS schema.

Key Procedures and Functions

The ETRM metadata documents 16 procedures and functions. Their purposes, based on naming and established EBS behavior, are as follows:

• AUDIT_FORM — Records form-level access activity for the logged-in session, supporting auditability of navigation to specific forms.
• AUDIT_RESPONSIBILITY — Records responsibility-level access, capturing which responsibility a user entered.
• AUDIT_WEB_RESPONSIBILITY — Performs the equivalent responsibility audit action for web (self-service) sessions.
• AUDIT_USER — Logs a user sign-on event, establishing the login record used by downstream session logic.
• AUDIT_USER_END — Closes the audit trail for a user session at sign-off.
• AUDIT_END — Finalizes session audit records during termination sequences.
• NEW_SESSION — Establishes a new FND_SESSIONS record for the authenticated user.
• NEW_ICX_SESSION — Creates an ICX (web/self-service) session, the web-tier counterpart to NEW_SESSION.
• NEW_PROXY_ICX_SESSION — Creates an ICX session on behalf of a proxied user.
• NEW_AOLJ_SESSION — Creates an AOL/J (Java) session used by EBS Java-based components.
• SET_SESSION — Binds the active session context (session identifier and related attributes) for subsequent processing.
• IS_PWD_EXPIRED — Returns whether the password for the user is expired, driving password-change enforcement.
• UPDATE_NAVIGATOR — Persists navigator (menu) state for the user's session.
• GET_NAVIGATOR_PREFERENCES — Retrieves stored navigator preferences for the user.
• GET_INVALID_LOGINS — Returns the count of invalid login attempts, supporting account-lockout logic.

Tables Accessed

FND_SIGNON reads and writes the core FND authentication and session tables via APPS synonyms. Login and user data are held in FND_USER, FND_LOGINS, FND_LOGINS_S, and FND_UNSUCCESSFUL_LOGINS, which record the user account, successful login history, audit shadow records, and failed attempts respectively. Session state is stored in FND_SESSIONS, ICX_SESSIONS, and FND_APPL_SESSIONS. Responsibility and form-level audit data reside in FND_LOGIN_RESPONSIBILITIES, FND_LOGIN_RESPONSIBILITIES_S, and FND_LOGIN_RESP_FORMS. Application metadata comes from FND_APPLICATION and FND_FORM. Desktop integration objects are tracked in FND_DESKTOP_OBJECT_ID_S and FND_USER_DESKTOP_OBJECTS. DUAL is used for scalar evaluation.

Usage Notes

FND_SIGNON is invoked indirectly by the standard sign-on path rather than through direct end-user calls: the APPLSYSPUB forms login routine, the web/ICX login (ICX_SEC, FND_WEB_SEC), single sign-on (FND_SSO_MANAGER), Oracle Applications Manager session management (FND_SESSION_MANAGEMENT), and Java AOL/J sign-on all route through it. Custom code should treat it as a low-level internal API; in a 12.1.1 or 12.2.2 instance, session and login logic is normally driven through supported public interfaces, and direct invocation risks corrupting FND_LOGINS or FND_SESSIONS integrity. Investigators examining failed or rogue logins typically query the audit tables populated by these procedures, while developers extend behavior by calling documented APIs rather than the package internals.