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-openapi

A CAP Java service whose two handlers call role collection endpoints through a client the Cloud SDK's OpenAPI generator builds at build time from a specification kept in the project.

srv/pom.xml runs openapi-generator-maven-plugin in the generate-sources phase over api-specs/AuthorizationAPI.yaml and writes the api and model packages into src/gen/java; the specification is the Swagger 2.0 document of the SAP Authorization and Trust Management service, whose own description says it lets you manage "roles, role templates, and role collections of your subaccount". AuthorizationServiceHandler holds DestinationAccessor.getDestination("xsuaa").asHttp() and a RoleCollectionsApi built on it as class fields, and maps the generated RoleCollection down to a CDS type carrying name and description only. The model is one function and one action and no entity, with cds.datasource.auto-config.enabled: false and h2 at runtime scope, so nothing is persisted. There is no README, and the repository description is what names the subject.

Facts

Last push

Where it sits

Lives in
Demonstrates
OpenAPICAPOpenAPIcapabilityHanding a description of the service to clients and tools — an API portal, a code generator, a partner who wants a contract before they write anything.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.
Flavors
Javafrom its runtime
Runs
Cloud Foundry
Requires
SAP Destination serviceSAP Destination serviceartifactThe generated client is constructed on a destination read at runtime, so the endpoint and the credentials of the API it calls come from there.SAP Authorization and Trust Management serviceSAP Authorization and Trust Management serviceartifactThe API the generated client calls: the specification in the project is that service's own Authorization API, and the handlers read and create role collections through it.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10
@miyasuta
maintainer

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
Java
Runs on
Cloud Foundry

As a sample

Form
does not say

Connections4

Details

Sources2
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-openapitree, pushes, contributors, CIchecked

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
runtimesjava
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-openapi
JSON
/artifacts/miyasuta-cap-openapi.json
MCP
Connecting an agent