SampleSampleA worked example you read or clone. Evidence: it demonstrates, it never provides.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 →
cap-oauth-destination
A sample that declares a destination for OAuth2UserTokenExchange in mta.yaml, so it is deployed with the application rather than created by hand in the cockpit.
Facts
Last push
Where it sits
Lives in
Demonstrates
DestinationsCAPDestinationsReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.
Requires
SAP Destination serviceSAP Destination serviceNamed as a dependency in its documentation.
Who is behind it
Mio YasutakeMio YasutakeMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- does not say
Connections
Group by
NodeRelationBasis
Functional
DestinationsDestinationsReaching remote systems without addresses or credentials in the codeSAP and community, unassessed
demonstrates
authored
demonstrates Destinations
Reaching remote systems without addresses or credentials in the code
Technical
SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems resolved at runtimesap official, btp
needs
authored
needs SAP Destination service
Named, credentialed addresses of other systems resolved at runtime
Download
Architecture
as mta.yaml states it at 6fa10d8, readDownload
SAP 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, btp
SAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp
cap-oauth-destination-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
cap-oauth-destination-destinations → cap-oauth-destination-srvStated in the descriptor, datamta.yaml, module cap-oauth-destination-destinations, requires srv-api
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- cap-oauth-destination-srvhana, SAP Destination service
- cap-oauth-destination-db-deployerhana
- cap-oauth-destination-destinationsSAP Authorization and Trust Management service, SAP Destination service
Documented, with no instance in the document
- @cap-js/hana requires SAP HANA Cloudcap-oauth-destination-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicescap-oauth-destination-srv
Bound in the descriptor, not joined to an entry
hana
README
quoted from miyasuta/cap-oauth-destination, readmiyasuta/cap-oauth-destination/README.mdthe maintainer’s wordsOn GitHub
Purpose
This repository demonstrates how to create a Destination for OAuth2UserTokenExchange using mta.yaml.
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 viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-cap-oauth-destination- JSON
- /artifacts/miyasuta-cap-oauth-destination.json
- MCP
- Connecting an agent