Insert into projects (id, project, icon_css_classes, created, created_by) values (5, 'Training', 'fa-credit-card fa-lg', localtimestamp, 'TEST1') Insert into projects (id, project, icon_css_classes, created, created_by) values (4, 'Documentation', 'fa-ambulance fa-lg', localtimestamp, 'TEST1') Insert into projects (id, project, icon_css_classes, created, created_by) values (3, 'Email Integration', 'fa-hand-grab-o fa-lg', localtimestamp, 'TEST1') Insert into projects (id, project, icon_css_classes, created, created_by) values (2, 'Load Software', 'fa-dot-circle-o fa-lg', localtimestamp, 'TEST1') Insert into projects (id, project, icon_css_classes, created, created_by) values (1, 'Maintain Support Systems', 'fa-awesome-face fa-lg', localtimestamp, 'TEST1') , created timestamp (6) with local time zone

Here's the DDL that I will use for the demo. Comparing a Classic Report with a secured Fetch call, showing the same data How to secure the Fetch API The top region is a regular classic report and the bottom region is a secured Fetch API call. The goal of this app: Show different cards based on :app_user.

Use login test1, test2 or test3 with any password. Instead of using OAuth, we will use First Party Authentication, allowing an APEX Session to securely connect to ORDS using the Fetch API. I was quite proud of the solution, but turns out there is a better way. In my last blog post, I explained how to make the Fetch API work against an APEX session using OAuth.

Oracle apex javascript api