PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

abapOAuthAzure

An 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.

An implementation of Enhancement Spot OA2C_SPECIFICS for Microsoft Azure, written against the OAuth 2.0 Client API in ABAP. It is that implementation and nothing around it: the README is a single sentence and names one source, the SAP help page Access Microsoft Azure using the OAuth 2.0 Client API, so which flows and scopes are involved, and how the client itself is configured, stay with that page rather than with this repository.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Provides
AuthenticationABAPAuthenticationcapabilityEstablishing 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

Gregor WolfGregor WolfPersonMaintains this
In the atlas: maintains 17, contributes to 59, wrote 2
@gregorwolf
maintainer

Before choosing this

Signals

ActivityQuietNo published releases; repository quiet for 27 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

Connections1

README

quoted from gregorwolf/abapOAuthAzure under Apache-2.0, read
gregorwolf/abapOAuthAzure/README.mdOn GitHub

abapOAuthAzure

Enhancement Spot OA2C_SPECIFICS implementation to support Microsoft Azure using the OAuth 2.0 Client API in ABAP. Based on the example at Access Microsoft Azure using the OAuth 2.0 Client API

Apache-2.0, read
Authentication
  1. abap_jwt_generatorGenerates signed JSON Web Tokens in ABAP
  2. abap-pwnedpasswordsChecks passwords against Have I Been Pwned from ABAP
  3. abap2oauth2ABAP API for OAuth 2.0 authentication
  4. abapNTLMHTTP NTLM client for ABAP
  5. abap_cloud_platformTypeScript library reaching ABAP service instances on Cloud Foundry
  6. decodesapsso2TypeScript decoder for MYSAPSSO2 logon tickets
  7. Cloud ConnectorSAP's on-premises agent linking SAP BTP to customer-network systems
  8. abap-aws-sigv4Signs outbound HTTP calls to AWS APIs with AWS Signature Version 4, directly from ABAP.

Details

Sources3
dotabapdiscovered herechecked
github.com/gregorwolf/abapOAuthAzuretree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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 configuration30
lines422
statements242
objects7
files8
analysed, main
abaplint version2.120.84
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:gregorwolf-abapoauthazure
JSON
/artifacts/gregorwolf-abapoauthazure.json
MCP
Connecting an agent