SAP Keystore Service
A repository for cryptographic keys and certificates in SAP BTP's Neo data centres, which an application retrieves at runtime for signing, encryption and SSL communication.
Application code that signs or verifies digital signatures, encrypts or decrypts messages, or performs SSL communication needs keys and certificates from somewhere other than its own bundle. SAP Keystore Service holds them as keystores, which the application retrieves and uses in those operations. It also covers client-certificate authentication, the standard authentication method in Java EE, and encryption of unlimited strength through the Java Cryptography Extension unlimited strength jurisdiction policy files installed on SAP JVM. Its one plan, Default, is listed in Neo data centres and in Moscow and Riyadh, with no Cloud Foundry region. In the regions marked Neo, SAP removes the service from the Eligible Cloud Services List on 31 December 2028, and no subscription there runs past that date.
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
Connections
Encrypting, decrypting and signing data from application code
Download
What’s New
from SAP Help Portal, readNo New Content
Others providing
Compare all 4 on the Encryption and signing page →- hhelibeb/blowfish-abaphhelibeb/blowfish-abapA Blowfish cipher implemented directly in ABAP after Bruce Schneier's definition, encrypting and decrypting strings in ECB and CBC mode through one class, on ABAP 750 or higher.independent, abapBlowfish cipher in ABAP, ECB and CBC modesfrom ABAP
- abapPGPabapPGPAn OpenPGP implementation in ABAP, scoped to signing and marked work in progress, whose own README warns that it will most certainly contain severe bugs and points to established PGP software.independent, abapOpenPGP implementation in ABAP, scoped to signingfrom ABAP
- Sumu-Ning/AESSumu-Ning/AESAES and Rijndael encryption and decryption utilities for ABAP, covering six cipher modes and three padding schemes, installed by copying the source or through abapGit.independent, abapAES and Rijndael encryption utilities for ABAPfrom ABAP
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
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-keystore- JSON
- /artifacts/btp-keystore.json
- MCP
- Connecting an agent