Discussion on "SaaS REST for VPD Multi-Tenant APEX Apps"

Matt Mulvaney · 2024-03-11T09:10:10.338Z

Whats this all about? In a SaaS model, APEX provides an apex_session.set_tenant_id procedure to set a context. This context can be accessed by your VPD in determining the rows the user can access. However with REST, I have some questions... How do y...

Hi Matt,

Fantastic write up!

Want to note that this example now requires the use of setting up an APEX session for an ORDS handler whereas before there was no APEX session. So, this adds a small amount of overhead to each REST call which VPD requires set up regardless. One may want to consider using their own custom Context that they manage the set up of it if that becomes an issue. It should not be an issue for most. The write up above is ideal for the majority! Just wanted to add that in.

Also, for point 14 you mentioned QuickSQL breaks without that grant? Mind sharing that part? I did not see mention of QuickSQL until that part so wondering if that is a typo or if not would like to investigate what is occurring.

Best, Neil

Regarding QuickSQL, I haven't been able to reliably reproduce. I'll keep the grant, but lose the reference to QuickSQL

Matt Mulvaney

You are correct! I just wanted to denote that there may be a need to deviate, but I believe creating a session, setting tenant_id, by the APEX API's is definitely preferred/only approach when using the provided tenant system from APEX. So, the write up is perfect.

I will raise an ER to see if there can be a version (specific for ORDS) that does not require creating an APEX session :)

Matt Mulvaney

Ah so if you create a prehook, and don't execute the grant, it sometimes breaks QuickSQL?

Search Hashnode

SaaS REST for VPD Multi-Tenant APEX Apps

Responses1