CapabilitySecurity & ComplianceStandard ABAP, read from its artifacts

Authentication

On ABAP the repositories here face outward, the system authenticating itself to someone else's API: a JWT from abap_jwt_generator, Azure through SAP's own OAuth 2.0 client in abapOAuthAzure by Gregor Wolf, NTLM in abapNTLM by Lars Hvam, and AWS Signature v4 in abap-aws-sigv4. abap-pwnedpasswords is the inbound one, checking a password against the Pwned Passwords breach list.

Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for Standard ABAP.

A Standard ABAP coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS
abap-pwnedpasswords

Wraps the Pwned Passwords API V3 so an ABAP program can check in one call whether a candidate password has appeared in a breach, returning a boolean or the fuller detail behind it.

A Standard ABAP coverage assessment has not been written. View all flavors

Artifacts3

3 of 3 artifacts
ArtifactSignals
Apps1
Cloud ConnectorSAP's on-premises agent linking SAP BTP to customer-network systems
Signals
none
Packages2
abap_cloud_platformTypeScript library reaching ABAP service instances on Cloud Foundry
Signals
none
abap-pwnedpasswordsChecks passwords against Have I Been Pwned from ABAP
Signals
none

Details

Coverage
statecommunity only, ABAP, Standard ABAP, derived
also inCAP, BTP/BAIP, UI5
For your agent
Ref
capability:authentication
JSON
/capabilities/authentication.json
MCP
Connecting an agent