onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.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 →Reference

cap-principal-propagation

An on-premise ABAP OData V2 service read through a named destination and the SAP Connectivity service, with a Fiori elements list report and an approuter in front of the CAP service.

cds.requires declares ZEPM_REF_APPS_PO_APV_SRV as kind: odata-v2 against the model imported into srv/external, with credentials.destination: 'abaptrialPP' and the path /sap/opu/odata/sap/EPM_REF_APPS_PO_APV_SRV under both [hybrid] and [production], and csrf and csrfInBatch both set. MyService.PurchaseOrders is a projection on the imported entity, and its one READ handler runs req.query against that connection. The MTA binds connectivity and destination on the lite plan and xsuaa to the service module, and the approuter in app/router forwards the auth token to it. The destination is not in the repository, so which authentication type it is configured with is outside what the project states; the README is the CAP scaffold's own and the repository's name is what names the subject.

GitHub3 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
DestinationsCAPDestinationscapabilityReaching 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.Service integrationCAPService integrationcapabilityUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
SAP Destination serviceSAP Destination serviceartifactThe remote service's credentials name a destination rather than an address, and the MTA binds a destination instance to the service module.SAP Connectivity serviceSAP Connectivity serviceartifactThe MTA binds a connectivity instance to the service module, which is what reaches an on-premise system through the Cloud Connector.@sap/approuter@sap/approuterartifactThe deployment includes an approuter module in front of the CAP service, configured to forward the auth token to it.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
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
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Form
does not say

Connections5

Download
cap-principal-propagation connectionscap-principal-propagationPROVIDES→ demonstrates2demonstrates authoredDestinationsdemonstrates authoredService integrationNEEDS→ needs3needs declared The deployment includes an approuter module in front of the CAP service, configured to forward the auth token to it. miyasuta/cap-principal-propagation — mta.yaml: https://raw.githubusercontent.com/miyasuta/cap-principal-propagation/main/mta.yaml@sap/approuterneeds declared The MTA binds a connectivity instance to the service module, which is what reaches an on-premise system through the Cloud Connector. miyasuta/cap-principal-propagation — mta.yaml: https://raw.githubusercontent.com/miyasuta/cap-principal-propagation/main/mta.yamlSAP Connectivity serviceneeds declared The remote service's credentials name a destination rather than an address, and the MTA binds a destination instance to the service module. miyasuta/cap-principal-propagation — package.json: https://raw.githubusercontent.com/miyasuta/cap-principal-propagation/main/package.jsonSAP Destination service

README

quoted from miyasuta/cap-principal-propagation, read
miyasuta/cap-principal-propagation/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-principal-propagationtree, 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
runtimesnode
deploymentCloud Foundry
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-principal-propagation
JSON
/artifacts/miyasuta-cap-principal-propagation.json
MCP
Connecting an agent