BrowseAll ecosystems
Everything in the atlas
5 of 2341
Type
Domain
Origin
Signals
More: 2
Group by: Kind
EntryBySignalsLast activity
Artifacts
@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, cap
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
@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, cap
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
@sap/xssec@sap/xssecToken validation and security context for XSUAA and IAS.sap official, cap
Token validation and security context for XSUAA and IAS
ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abap
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
com.sap.cds:cds-feature-xsuaacom.sap.cds:cds-feature-xsuaaThe CAP Java feature that validated XSUAA-issued JWTs, published up to 2.10.7 before CAP Java 3.0 removed it in favour of com.sap.cds:cds-feature-identity.sap official, cap
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0