The privs have to be local to the schema.
So the best you could do is create a VIEW in the same schema, that queries the table, then auto-enable that view, and add the priv to your cilent.
Hi Jeff, thanks for your answer. We made a Synonym because we need to update, delete and insert but it is not being listed in APEX to be enabled as an autoRest resource. How should I grant it? As which user should I create it?
Coming back to schemas and privileges, what could I do to give security to my endpoints in other schemas?
My schemas CAR, HOUSES, are exposed through the following Uris: /ords/car(schema)/module/template, in a way that we could segment our resources properly.
I know I can centralize everything in only one schema, but in that way, I am losing the different endpoints + schema combinations, and the auto rest feature.
Thanks in advance
you need an application schema, with all of your endpoints based there, then you can have a single oauth client with the appropriate privileges assigned
otherwise you need one oauth client per schema
Are you going to think about making OAuth clients cross-schema in the future? Cause many of our Clients will consume information from different schemas, and I can not make them request another token when changing from one schema to another. It is complex to maintain in the near future and not too agile regarding the operational point of view.
I think that could be a great advantage considering big enterprise companies like this one that runs their different applications in 1 huge DB.
Thank you very much for your help