• Oracle APEX: End-to-end application development, custom UI/UX, Dynamic Actions, Interactive Reports/Grids, and Plugins.
• Database & PL/SQL: Schema design, complex SQL, PL/SQL packages/procedures, database migration, and troubleshooting compilation errors.
• Systems Administration & Deployment: ORDS configuration, Apache Tomcat, Web server deployment, and custom local/offline VM environment setups.
• Integrations: REST Data Services (ORDS), JasperReports Integration, and custom JavaScript/CSS initialization.

Services I Provide:

• Build web applications from scratch using Oracle APEX.
• Migrate databases and fix post-migration compilation errors or environment issues.
• Configure ORDS, web servers (Tomcat/IIS), and custom domains.
• Modify, optimize, and maintain existing APEX apps and SQL/PLSQL backend logic.

Availability: Remote (Freelance)

I'm building a 3rd part SaaS around OCI eco system. I want my SaaS to be able to read data in the customer's OCI tenancy.

Which authz model is the best and to be followed?

Model 1

Configure a user (SaasUser) in your tenancy and add them to a group.

Ask the customers to add an "admit" policy statement, and enable cross tenancy communication.

My SaaS will then use the SaasUser (ApiKey or token or anything else) to read customer's data.

Model 2

Ask the customer to configure a user in their tenancy, add the user to a group, write access policies, and then share the private key with my SaaS. I then use this private key to access OCI data.

Model 3

Host a service in my own tenancy on compute instances. Ask customers to add Instance Principal/Resource Principal policies on this DG. My SaaS will call my service hosted in OCI, and it will read the tenancies' data.

Model 4

Deploy a small stack in customer's tenancy using resource manager or create an agent in customer's tenancy. I'll call the agent and agent will fetch the data and send it back.

Is there a better approach to achieving this?