SAP Gateway runtime odata path permissions -


is there standard way change runtime permissions user able call odata resources of sap gateway service, other manually writing code in every service implementation method check if request allowed?

for example, based on setting in customizing, odata paths below /foo , /bar user x should forbidden, i.e. http get/post/delete <host>:<port>/foo/test , http get/post/delete <host>:<port>/bar/test should yield http 403 user x, http get/post/delete <host>:<port>/something should ok.

is there way can controlled @ single place rather being required implement check in every method implementing odata requests?

the proper place authorization check in backend method. authorization error should populate service , yield 403 example.

if reason don't want that, write own http handler , insert in sicf called on paths.

the standard role setup allows access or no access service, "pattern" access referring missing. can't understand why want it? make odata services kind of un-predictable consumer, wouldn't it?


Comments

Popular posts from this blog

dns - How To Use Custom Nameserver On Free Cloudflare? -

python - Pygame screen.blit not working -

c# - Web API response xml language -