Results for “security_group_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WFA_SEC is the Oracle Workflow security and web-session management package in the APPS schema, declared with AUTHID CURRENT_USER. Its documented role is to create, validate, retrieve, and destroy HTTP-cookie-based web sessions for Oracle E-Business Suite clients, and to render the login, header, and footer fragments of the Workflow self-service web pages. The package is the enforcement point that ties an authenticated FND_USER identity to a browser session, and it also supports pseudo-sessions for users who enter the applications from an e-mail notification link rather than through the standard login page. A package-level flag, validate_only, allows callers to perform session validation without displaying the login dialog; the Workflow Monitor uses it to test an access key after a failed session retrieval, and detached notification viewing uses it to determine whether a valid session already exists.

Key Procedures and Functions

• CREATESESSION — creates a new web session for a supplied user name and password, with session data normally persisted on the client as an HTTP cookie. Documented errors include an invalid user name or password and an inability to create the session.
• PSEUDOSESSION — creates a temporary ICX pseudo-session for a user arriving from an e-mail notification containing a link into the applications. Only the ICX implementation acts on it; other implementations are no-ops.
• GETSESSION — returns the user name associated with the session information held by the client, typically read from an HTTP cookie. Fails when no valid session is in effect or session information cannot be read.
• HEADER / FOOTER — emit the HTML header and footer for Workflow web pages.
• DETAILURL — constructs the detail-page URL used by Workflow web rendering.
• CREATE_HELP_SYNTAX — generates the help syntax (help target linkage) used by Workflow web pages; this is the routine associated with the search term "create_help_syntax".
• GET_ROLE_INFO, GET_ROLE_INFO2, GET_ROLE_INFO3 — progressive variants that return role information for security and navigation decisions.
• RESETCOOKIE — clears the session cookie on the client.
• GET_PROFILE_VALUE — reads a profile option value for the current context.
• LOCAL_CHR — character/encoding helper used when composing web output.
• DIRECTLOGIN — performs a login without the interactive dialog, used for programmatic entry.
• GETFWKUSERNAME — returns the Workflow user name for the current session.
• LOGOUT — terminates the current web session.
• DS_COUNT_LOCAL_ROLE, DS_UPDATE_LOCAL_ROLE — count and update the local (WF_LOCAL) role cache, used to keep the Workflow directory in step with changes.
• GETUSER, USER_ID — resolve the current user and the numeric user identifier.

Tables Accessed

The package reaches its data through APPS synonyms. FND_USER supplies user name and password authentication for session creation and login routines. WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES hold the Workflow local directory of roles and user-to-role assignments backing the GET_ROLE_INFO family and the DS_* role synchronization routines. DBMS_SESSION is used to manage session-level state, and HTP and OWA_COOKIE provide HTML generation and HTTP cookie read/write for session persistence.

Usage Notes

WFA_SEC is not exposed as a runnable concurrent program or form. It is invoked internally by the Oracle Workflow self-service web pages, by the Workflow Monitor, by notification handling and detached notification viewing, and by any custom JSP, servlet, or PL/SQL page that needs to establish or validate an EBS web session. Custom code typically calls CREATESESSION for explicit login, GETSESSION to test for an existing session, and LOGOUT or RESETCOOKIE to end one. Because the package is referenced by roughly thirty other packages and its state depends on cookie and session context, it must be called from within the web request flow rather than from a background batch job.