Maintain outbound connectivity

Needed for outbound API connectivity

provide-abap relies upon the API microservices of the PRVD Stack. For demonstration purposes, we will use these instances of the PRVD API microservices

• ident.provide.services

• baseline.provide.services

• vault.provide.services

• nchain.provide.services

• privacy.provide.services

In transaction STRUST, upload the following certificates to ensure your SAP system can call the given PRVD stack services. Additional details can be found in the certificates directory of the provide-abap repo.

• provide.services client API certificate

• AWS root certificates (Starfield and Amazon Root CA 1)

The exact client / root certificates required if you are using PRVD stack APIs from an alternate host/subdomain or through a middleware.

Check the certificates directory of the provide-abap repo for more instructions on using transaction code STRUST and required root/client certificats

PRVD API outbound connectivity alternatives

If the direct outbound connectivity to these PRVD APIs cannot be achieved you can choose one of these options

• Create middleware pass-throughs to the PRVD APIs. You would want to ensure your middleware systems use the same OpenAPI specification for both the sender and receiver side for the PRVD APIs

• Interested parties can run these PRVD stack APIs from their own dedicated hosts as well if they so wish. Additional info will be provided soon for enterprise clients wishing to run their own instance internally of the PRVD stack.