Non-functional design
In Chapter 4, Security and Connectivity, and Chapter 5, Non-Functional Design for Operability, we extensively covered important non-functional design elements. If you need to refresh your memory, just scroll back and have a look. Here, let’s briefly point out how SAP BTP application development services cater to some non-functional requirement categories:
- Security: You can bind applications to the XSUAA service so that they can utilize the authentication and RBAC capabilities. This binding can be done by running ad hoc commands or can be specified as a deployment element. Through XSUAA, applications can be made accessible only after the user authenticates, including the identity federation and single sign-on (SSO) capabilities provided by SAP Identity Authentication Service and/or the corporate identity provider. Similarly, by adding security specifications, such as role and role template definitions, the application can check a user’s authorizations...
