Everything in the atlas
Type
Domain: 2
Origin
Signals
More: 2
Group by: Capability
SQL templates for HANA audit policies of an S/4HANA tenant
Ingests and retains compliance audit data from BTP
TechEd 2022 session on SAP BTP security recommendations
Hands-on applying SAP BTP security recommendations to a trial account
XSUAA authentication stack for an MCP server on SAP BTP
It stops at the `AuthInfo` and the raw bearer token, and the README lists what stays with the consuming server: rate limiting, the scope and tool policy, the MCP transport, the SAP HTTP client's headers, and helmet-style hardening. The one piece of hardening it constrains rather than defers is the cross-origin opener policy, which it deliberately leaves unset because popup-based OAuth breaks under it. It is ESM-only on Node 22 or later and shares the host's Express and MCP SDK instances as peer dependencies, so a server on Express 4 cannot take it.
Browser login and session module for SAP MCP servers
The maintainer states it is unofficial, not endorsed by SAP, and that it automates authenticated SAP web endpoints and browser session cookies in ways SAP's terms of service or an organisation's own policies may restrict. Password login is confined to `accounts.sap.com` and the standard SAP Cloud Identity Services tenant domains: a custom IAS domain, or a login that conditional authentication delegates to a corporate identity provider, fails closed before the password is filled and has to be completed through an interactive login instead.
SAP's Node.js application router in front of business applications
OAuth2 token fetcher for a Cloud Foundry app's XSUAA binding
TypeScript library reaching ABAP service instances on Cloud Foundry
SAP's on-premises agent linking SAP BTP to customer-network systems
Identity Authentication and Identity Provisioning as one tenant
OAuth 2.0 grant flows for applications and APIs in Neo regions
OAuth server issuing JWTs and holding scopes for BTP apps
Registration, login and consent for customer-facing sites
UI5 app reading the signed-in user via launchpad and approuter
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The repository publishes no licence, so reusing its code needs the author's permission.
TechEd 2022 session on SAP BTP security recommendations
Hands-on applying SAP BTP security recommendations to a trial account
OAuth 2.0 grant flows for applications and APIs in Neo regions
OAuth server issuing JWTs and holding scopes for BTP apps
MTA projects sharing a role collection across role templates
Neither the package manifest nor the repository tree declares a licence.
Java apps showing policy-based authorization with AMS on SAP BTP
Node.js apps showing policy-based authorization with AMS on SAP BTP
Hands-on applying SAP BTP security recommendations to a trial account
Serves BTP applications under the customer's own domain
Registration, login and consent for customer-facing sites
APIs for retention, deletion and personal data reports
Retention rules triggering blocking, deletion and archiving
Service answering data subjects about their stored personal data
Key and certificate repository in SAP BTP's Neo data centres
Provisioning jobs carrying users and groups between systems
Postman collections for the SAP Analytics Cloud SCIM API
Postman collection for the SAP Concur User Provisioning Service APIs
Identity Provisioning jobs syncing SAP Concur users for Joule
Hands-on integrating Cloud Identity Services with Microsoft Entra
Scans uploaded files over REST with ClamAV
API proxies with security and traffic policies and Developer Hub
Vault for an application's passwords, keys and keyrings
Tracks vulnerabilities in open-source components of BTP apps
Rule-based resolution of SAP S/4HANA business situations
Low-code and no-code tool for business processes and RPA bots
Files for two Japanese posts on BTP user registration with SAP Build
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The repository publishes no licence, so reusing the files needs the author's permission. Nothing here says what each file contains, and the two posts they were published for are in Japanese.
Resolves who is responsible for a process or item, and notifies them