PackagePackageA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
abap-aws-sigv4
Signs outbound HTTP calls to AWS APIs with AWS Signature Version 4, directly from ABAP.
The README starts from there being no AWS SDK for ABAP, which leaves the Signature Version 4 signing process to be built by hand. ZAWS_SIGV4_UTILITIES implements that process against AWS's own documentation of it, and three example classes cover the three cases AWS documents: GET with an authorization header, POST, and GET with the authentication information in the query string. Running an example needs AWS access and secret keys, and the README says you might want to import the relevant certificates into STRUST for a call to an HTTPS endpoint, with the openssl command for reading them off the endpoint.
Facts
Last pushLicenceMIT
Where it sits
Lives in
Provides
AuthenticationABAPAuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. [Authorization](capability:authorization) decides what that identity may do; [identity provisioning](capability:identity-provisioning) manages its lifecycle across systems.
Who is behind it
tmhewtmhewMaintains this
In the atlas: maintains 1, contributes to 1@tmhewmaintainer
In the atlas: maintains 1, contributes to 1@tmhewmaintainer
Before choosing this
Signals
ActivityQuietNo published releases; repository quiet for 58 months
It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.
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
Group by
NodeRelationBasis
Functional
AuthenticationAuthenticationEstablishing who is calling and making that identity availableSAP and community, narrow by design
provides
stated
provides Authentication
Signs outbound calls to AWS APIs with AWS Signature Version 4 from ABAP, following AWS's own signing process, with worked examples for an authorization header, a POST and the query string.
“Now, you can call AWS API directly with AWS Signature v4 authentication.”“This implementation is based on AWS documentation [Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html).”
Establishing who is calling and making that identity available
Technical
connects to
stated
connects to Amazon Web Services
Calls to an AWS API, signed with Signature Version 4; the three example classes call AWS endpoints, and the README names importing the endpoint's certificate into STRUST for an HTTPS call.
“Now, you can call AWS API directly with AWS Signature v4 authentication.”“You might want to import the relevant certificates to `STRUST` if you are making a call to a HTTPS endpoint.”
Amazon's cloud platform, with accounts, regions, a command-line interface and CloudFormation templates that provision resources. For the things here it is the account an SAP tool is deployed into, next to the SAP systems it reads from.
Download
README
quoted from tmhew/abap-aws-sigv4 under MIT, readtmhew/abap-aws-sigv4/README.mdthe maintainer’s wordsOn GitHub
AWS Signature V4 for ABAP
Wanted to extend to AWS but there isn't AWS SDK for ABAP? Now, you can call AWS API directly with AWS Signature v4 authentication.
This implementation is based on AWS documentation Signature Version 4 signing process. You can look at ZAWS_SIGV4_UTILITIES for implementation details and the following examples for usages. You will need to provide AWS access and secret keys to run the examples.
| Example | Documentation |
|---|---|
| ZAWS_SIGV4_EXAMPLE_001 | Using GET with an authorization header |
| ZAWS_SIGV4_EXAMPLE_002 | Using POST |
| ZAWS_SIGV4_EXAMPLE_003 | Using GET with authentication information in the Query string |
Refers to AWS Documentation for the list of APIs that you can use. You might want to import the relevant certificates to STRUST if you are making a call to a HTTPS endpoint. Below is an example on how to retrieve the certificates for a HTTPS endpoint.
openssl s_client -connect ec2.amazonaws.com:443 -showcertsMisc
Others providing
Compare all 23 on the Authentication page →AuthenticationAuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. Authorization decides what that identity may do; identity provisioning manages its lifecycle across systems.SAP and community, narrow by design
- abap_jwt_generatorabap_jwt_generatorGenerates a signed JSON Web Token in ABAP from an explicit header and claim, a stored profile in table ZJWT_PROFILE, or a shared secret, signing through a PSE profile or with the secret.independent, abapGenerates signed JSON Web Tokens in ABAPfrom ABAP
- @arc-mcp/xsuaa-auth@arc-mcp/xsuaa-authThe client-to-server authentication stack for an MCP server on SAP BTP: an XSUAA OAuth proxy, dynamic client registration, a chained bearer verifier, and a separate entrypoint for per-user principal propagation.independent, btpXSUAA authentication stack for an MCP server on SAP BTPfrom BTP/BAIP
- abap-pwnedpasswordsabap-pwnedpasswordsChecks from ABAP whether a password appears in the Have I Been Pwned breached-password list, wrapping the Pwned Passwords API V3 in one call that answers with a boolean.independent, abapChecks passwords against Have I Been Pwned from ABAPfrom ABAP
- 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
- 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, btpIdentity Authentication and Identity Provisioning as one tenantfrom BTP/BAIP
- SAP Customer Identity and Access Management for B2CSAP Customer Identity and Access Management for B2CSAP's customer identity service: registration, login and consent for the users of a company's websites and apps, kept in one profile per customer, with regional data storage and risk-based authentication as options.sap official, btpRegistration, login and consent for customer-facing sitesfrom 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-feature-identitycom.sap.cds:cds-feature-identityThe CAP Java feature that validates OAuth2 tokens from XSUAA and SAP Cloud Identity Services and builds the request's security context from them.sap official, capOAuth2 token validation from XSUAA and SAP Cloud Identity Servicesfrom CAP
- 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, capFormer XSUAA JWT validation for CAP Java, removed in CAP Java 3.0from CAP
- abapOAuthAzureabapOAuthAzureAn Enhancement Spot OA2C_SPECIFICS implementation for Microsoft Azure, written against ABAP's OAuth 2.0 Client API, with a one-sentence README that leaves configuration to SAP's help page.independent, abapOA2C_SPECIFICS implementation for Microsoft Azure OAuth 2.0 in ABAPfrom ABAP
- abap2oauth2abap2oauth2An ABAP API for OAuth 2.0 authentication that registers a provider's client ID and secret as a named consumer and implements signature method 3, the one Google uses.independent, abapABAP API for OAuth 2.0 authenticationfrom ABAP
- abapNTLMabapNTLMAn HTTP NTLM client for ABAP, with the RC4, MD4 and DES algorithms the protocol needs implemented in ABAP, which its maintainer says seems to work only some of the time.independent, abapHTTP NTLM client for ABAPfrom ABAP
- abap_cloud_platformabap_cloud_platformA TypeScript library of the Cloud Foundry calls that walk down to an ABAP service instance, read its SAP_ADT service key and log a user in, so a tool outside the system can reach it.independent, btpTypeScript library reaching ABAP service instances on Cloud Foundryfrom BTP/BAIP
- decodesapsso2decodesapsso2A TypeScript library that decodes a MYSAPSSO2 logon ticket into its user, client, system and validity fields, and returns the signature without validating it, so it never shows a ticket is genuine.independent, abapTypeScript decoder for MYSAPSSO2 logon ticketsfrom ABAP
- @marianfoo/sap-mcp-auth@marianfoo/sap-mcp-authA shared browser-login and session module for SAP MCP servers: it drives a Playwright browser through SAP Identity Authentication, caches the session cookies and returns a cookie header an HTTP client can send.independent, btpBrowser login and session module for SAP MCP serversfrom BTP/BAIP
- @sap/approuter@sap/approuterSAP's Node.js application router: the single entry point in front of a business application's microservices, which authenticates the user, forwards each request to a backend by route and serves static content.sap official, btpSAP's Node.js application router in front of business applicationsfrom BTP/BAIP
- @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
- Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btpSAP's on-premises agent linking SAP BTP to customer-network systemsfrom BTP/BAIP
- @sap/xssec@sap/xssecToken validation and security context for XSUAA and IAS.sap official, capToken validation and security context for XSUAA and IASfrom CAP
- cds-azure-adcds-azure-adAzure AD and Azure AD B2C as a custom-defined authentication strategy for CAP through passport-azure-ad, implementing the hook capire documents so the application does not validate tokens itself.independent, capAzure AD and Azure AD B2C authentication strategy for CAPfrom CAP
- @saptools/cf-xsuaa@saptools/cf-xsuaaA command line and Node.js API that reads the XSUAA binding of a Cloud Foundry app and prints an OAuth2 client_credentials token for it, cached until it expires.independent, btpOAuth2 token fetcher for a Cloud Foundry app's XSUAA bindingfrom BTP/BAIP
- cds-common-jwt-supportcds-common-jwt-supportJWT authentication for CAP without xsuaa or xssec, validating tokens with jose instead, for a service that authenticates against an identity provider other than XSUAA; last released in April 2022.independent, capJWT authentication for CAP without xsuaa or xssecfrom 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
discovered viadotabap
first seen in the atlas
ecosystem and domainabap, security-and-compliance
abaplint
issues under its own abaplint configuration308
lines578
statements259
objects5
files8
analysed, main
abaplint version2.120.84
read fromabaplint.app,
History in the atlas
- First seen.
For your agent
- Ref
artifact:tmhew-abap-aws-sigv4- JSON
- /artifacts/tmhew-abap-aws-sigv4.json
- MCP
- Connecting an agent