sap-usi-authority-check
A helper class, /USI/CL_AUTH, that checks whether the current user is authorized for the running transaction, mandatory for SchwarzIT's USI reports under their internal development guidelines.
USI's own reports each needed the same authority check, so /USI/CL_AUTH centralises it into one helper class instead of repeating the check in every report. Internal development guidelines make it mandatory for all USI reports, which is why many of SchwarzIT's other USI developments depend on it. Installing it needs no further dependencies and no special authorizations of its own.
Facts
Where it sits
Who is behind it
In the atlas: maintains 3@SchwarzITmaintainerDaniel ScholdeiContributes to this
In the atlas: contributes to 1@danielScholdeij-flachsContributes to this
In the atlas: contributes to 1@j-flachsJörg NeumannContributes to this
In the atlas: contributes to 3@NeumannJoergPatrick HahnContributes to this
In the atlas: contributes to 3@patrick2464 contributors
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Deciding who may read or change what, down to instance level
Download
README
quoted from SchwarzIT/sap-usi-authority-check under Apache-2.0, read
USI Authority Check
Purpose
This repository contains the helper class /USI/CL_AUTH that checks, if the user is authorized for the current transaction.
The class is very simple and would not be worth sharing, but according to our internal development guidelines, it must be used in all USI reports to secure them against unauthorized access.
Because of this rule, many of our developments depend on this class.
Installation Guide
This component has no dependencies and no special authorizations are required.
It is recommended to create the repository using the follwing settings.
| Field | Value |
|---|---|
| Git Repository URL | https://github.com/SchwarzIT/sap-usi-authority-check |
| Package | /USI/AUTH_MAIN |
| Display Name | USI Authority Check |
| Labels | SchwarzIT |
Note: The package name must start with /USI/ to avoid issues when pulling the repository.
How to contribute
Please check our contribution guidelines to learn more about this topic.
History
Others providing
Compare all 9 on the Authorization page →- SAP Authorization and Trust Management serviceSAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btpOAuth server issuing JWTs and holding scopes for BTP appsfrom BTP/BAIP
- OAuth 2.0 on SAP BTPOAuth 2.0 on SAP BTPOAuth 2.0 protection for applications and APIs on SAP BTP, listed in Neo regions: the authorization code grant for web applications and the client credentials grant for API and IoT scenarios.sap official, btpOAuth 2.0 grant flows for applications and APIs in Neo regionsfrom BTP/BAIP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- cap-toolkitcap-toolkitA utility bundle for CAP handlers, with a chainable HandlerBuilder, role checks, validation rules and query helpers, collecting boilerplate that otherwise repeats across projects into one dependency.independent, capUtility bundle for CAP handlers: builder, roles, validation, queriesfrom CAP
- @sap/ams-dev@sap/ams-devCompiles the DCL authorization policies of SAP's Authorization Management Service to DCN, so an AMS-secured application runs and is tested on a laptop.sap official, capCompiler from AMS DCL policies to DCN for local runs and testsfrom CAP
- @sap/ams@sap/amsDecides what a signed-in user may do in a Node.js application that authenticates through SAP Cloud Identity Services, from policies written in DCL.sap official, capAuthorization from DCL policies for Node.js apps on SAP Cloud Identityfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
- cds-entra-idcds-entra-idA CAP plugin that maps Microsoft Entra ID groups and app roles onto cds.User roles, so @requires and @restrict keep working for a CAP app hosted on Azure App Services.independent, capMaps Microsoft Entra ID groups and app roles onto cds.User rolesfrom CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
abaplint
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:schwarzit-sap-usi-authority-check- JSON
- /artifacts/schwarzit-sap-usi-authority-check.json
- MCP
- Connecting an agent