ORDS grabs connection from your pool to run your session.
It starts as ORDS_PUBLIC_USER - but the first thing it does is proxy connect as the user schema for which the service is defined.
So if I publish a RESTFul Service in the HR schema, when it runs, it runs as user HR
Ok, thanks for the response. It seems the problem is when I have a workspace with multiple schemas associated to it, if I define a restful service based on one of the schemas in that workspace the problem starts to raise. I unregistered that schema in the workspace and so far the problem is gone.