Discussion
Popular posts
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
Hey Neil. Thanks for your nice comments. Using apex_session.set_tenant_id is the standard, built-in, method of setting a tenant in APEX, is it not? Unfortunately this procedure does require an APEX session first (See my evidence below - and I also point out that this requirement isn't stated in the documentation). Therefore yes, using this standard approach adds an overhead to REST because of the requirement to establish a session first (i.e REST must set the context in the same consistent way as APEX does - i.e using apex_session.set_tenant_id). A custom context would be quicker for sure. I'll update the blog with a note, however I didn't want this blog to deviate from something is effectively the standard approach for VPD/SaaS for APEX. Is there possibility to remove this requirement (i.e to establish a session first) from apex_session.set_tenant_id a future release of APEX?
