Establishing who is calling — validating a token, resolving the user and their roles, and making that available for the rest of the request. Taking SAP Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp as the identity interface for everything SAP makes it SAML 2 or OIDC against Identity Authentication rather than XSUAA alone, with the user lifecycle carried by SCIM 2 replication into each service. AuthorizationAuthorizationDeciding who may read or change what, at service, entity and instance level — role checks, forwarded user context, and restrictions evaluated as query filters rather than after the fact.SAP and community, unassessed is still designed per system after that, since an S/4HANA role and a BTP role collection are different objects.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Activates a Spring Security configuration that enforces authentication on every endpoint once the required libraries are on the classpath and an XSUAA or Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp instance is bound; accepts either, or both from the same application.
Validated XSUAA-issued JWTs and built the security context for a CAP Java application before CAP Java 3.0 removed it; applications on the standard security configuration and a CAP starter bundle needed no code changes to move to its replacement.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Neither the package manifest nor the repository tree declares a licence.
Before CAP Java 3.0, XSUAA token validation lived in its own cds-feature-xsuaa module, separate from IAS support. The 3.0 release removed cds-feature-xsuaa and unified XSUAA and IAS behind cds-feature-identity, the module that now provides both.
Guidance to add cds-feature-xsuaa as a Maven dependency for authentication in a CAP Java project. It was removed in the 3.0 line, mid-2024 — cds-feature-identity is the replacement for XSUAA as well as IAS.
capability:authentication