Search Results jtf_auth_domain_name

Overview

The JTF_AUTH_READ_PERMS table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module, serving as a denormalized repository for authorization data. Its primary role is to store the direct, resolved mapping between a user (principal), a specific permission, and the security domain in which that permission is granted. This table acts as a performance-optimized cache or snapshot of the effective permissions derived from a user's role memberships and associated permission sets, as defined in the more complex, normalized JTF authorization tables. In the context of EBS 12.1.1 and 12.2.2, it is a critical component for runtime security checks, enabling the application to quickly determine if a user has the necessary read-level access to a given resource or function within a specified domain.

Key Information Stored

The table's structure is designed to store the essential triad of authorization: the user, the permission, and the context. The key columns, as indicated by the foreign key relationships, are the surrogate IDs that link to the master definitions. The JTF_AUTH_PRINCIPAL_ID column identifies the user or principal. The JTF_AUTH_PERMISSION_ID column specifies the exact permission being granted. The JTF_AUTH_DOMAIN_ID column defines the security domain or context for which the permission is valid. The primary key, JTF_AUTH_READ_PERMISSION_ID, is a unique identifier for each record. The description also notes the existence of denormalized name columns (JTF_AUTH_PRINCIPAL_NAME, JTF_AUTH_PERMISSION_NAME, JTF_AUTH_DOMAIN_NAME), which likely store the textual identifiers for easier reporting and debugging without requiring joins to the base tables.

Common Use Cases and Queries

A primary use case is auditing and reporting on user permissions. System administrators can query this table to generate a comprehensive list of all effective read permissions granted across the system. Another critical use is troubleshooting authorization issues, where developers can verify if a specific permission mapping exists for a user. Common SQL patterns include querying permissions for a specific user or verifying access to a particular permission within a domain.

• List all permissions for a user: SELECT * FROM jtf.jtf_auth_read_perms WHERE jtf_auth_principal_name = 'USERNAME';
• Find all users with a specific permission: SELECT jtf_auth_principal_name FROM jtf.jtf_auth_read_perms WHERE jtf_auth_permission_name = 'PERM_NAME' AND jtf_auth_domain_name = 'DOMAIN_NAME';
• Audit permissions across a domain: SELECT jtf_auth_principal_name, jtf_auth_permission_name FROM jtf.jtf_auth_read_perms WHERE jtf_auth_domain_name = 'DOMAIN_NAME' ORDER BY 1, 2;

Related Objects

The JTF_AUTH_READ_PERMS table is centrally linked to the master definition tables of the JTF authorization model via foreign key constraints. These documented relationships are fundamental for understanding its data lineage.

• JTF_AUTH_PRINCIPALS_B: The JTF_AUTH_PRINCIPAL_ID column in JTF_AUTH_READ_PERMS references this table to resolve the user or principal entity.
• JTF_AUTH_PERMISSIONS_B: The JTF_AUTH_PERMISSION_ID column in JTF_AUTH_READ_PERMS references this table to resolve the specific permission definition.
• JTF_AUTH_DOMAINS_B: The JTF_AUTH_DOMAIN_ID column in JTF_AUTH_READ_PERMS references this table to resolve the security domain context.

This table is typically populated and maintained by the underlying JTF security administration processes and should not be modified directly via DML operations.