Introduction
Following below we can implement Role based Authorization in Oracle APEX Application, in version 5.
Steps To Follow
Create below
Application Item: USER_ROLE
Table: ROLE_ACCESS_CONTROL
The purpose of this table is to store the privileges on Regions, Buttons and Items, for each role. Page access is controlled through the Region access (Even if one Region in a Page is given access, its Page will appear; Components cannot be created without a “Region”;)
| Column Name | Data Type | Comments |
| ROLE_ACCESS_ID | NUMBER | Primary Key |
| USER_ROLE | VARCHAR2(30) | Role Name |
| APP_ID | NUMBER | APEX System Variable |
| PAGE_ID | NUMBER | APEX System Variable |
| REGION_ID | NUMBER | APEX System Variable |
| COMPONENT_ID | VARCHAR2(30) | APEX5 System Variable |
| COMPONENT_NAME | VARCHAR2(30) | APEX5 System Variable |
| COMPONENT_TYPE | VARCHAR2(30) | APEX5 System Variable |
| DISPLAY_IND | CHAR(1) | Flag to Display/Hide a Component |
| READONLY_IND | CHAR(1) | Flag to set Read-Only for an Item |
| CREATED_BY | NUMBER | WHO columns |
| CREATED_DATE | DATE | |
| UPDATED_BY | NUMBER | |
| UPDATED_DATE | DATE |
User Interface:
Authorization Schemes to be created:
- List_Access – To control the Menu items
- Role_authorization – To control access to all components
- Role_authorization_readonly_item – To control the read-only property of an item, through the authorization scheme
To enable the menu, in the Navigation:
Set the SECURITY AUTHORIZATION SCHEME with the custom authorization scheme created (“ROLE_AUTHORIZATION”), for all Pages, Regions and Buttons.
Set the READ ONLY property as below, for all the Items which needs to be controlled as READ-ONLY:
Call To Action
For Oracle apex development and customization please do contact our company website https://doyensys.com/
Conclusion
Following above we can implement Role based Authorization in Oracle APEX Application.
