FIORI_SAPUI5intermediate
Fiori Security and Authorizations
Front-end and back-end authorizations, OData service activation and troubleshooting access errors.
Overview
Front-end and back-end authorizations, OData service activation and troubleshooting access errors.
Lessons in this topic
- Fiori Security Part 1: Front-End vs Back-End AuthorizationsUnderstand the two layers of Fiori security: front-end authorizations that allow launching apps and calling OData services, and back-end authorizations that protect business data — in hub and embedded deployments.
- Fiori Security Part 3: Troubleshooting 403s, Missing Data and Authorization ErrorsDiagnose access problems quickly: HTTP 401/403 in the browser, gateway error logs, back-end SU53 and authorization traces, CDS access control effects, and how to fix roles without over-authorising users.
- Fiori Security Part 2: Activating OData Services and ICF NodesMake OData services available safely: activating V2 services with /IWFND/MAINT_SERVICE, publishing V4 service groups with /IWFND/V4_ADMIN, system aliases, ICF nodes, and keeping activations consistent across the landscape.
Interview questions covered
- Explain how security works for a Fiori app end to end.
- How do you make sure OData services are correctly available across DEV, QA and PROD?
- A user reports a Fiori app shows an authorization error. How do you resolve it without over-authorising?