Skip to content

[SAP] add SAPKMSCryptoPlugin and PerSecretKEKStoreAdapter for SAP KMS…#30

Draft
rajivmucheli wants to merge 1 commit into
stable/2024.2-m3from
kms
Draft

[SAP] add SAPKMSCryptoPlugin and PerSecretKEKStoreAdapter for SAP KMS…#30
rajivmucheli wants to merge 1 commit into
stable/2024.2-m3from
kms

Conversation

@rajivmucheli
Copy link
Copy Markdown

… integration

  • Introduces SAPKMSCryptoPlugin, a Fernet-based crypto engine compatible with Barbican’s upstream plugin interface.
  • Adds PerSecretKEKStoreAdapter, enabling per-secret KEK resolution via user metadata (sap_gtid).
  • Replaces legacy ToyCryptoPlugin references with SAPKMS equivalents.
  • Updates setup.cfg entry points and barbican.conf to register sap_kms_crypto and sap_kms_adapter.
  • Ensures full compatibility with upstream Barbican cbase DTOs and plugin manager.
  • Includes improved logging, safe key handling, and transient plugin_meta propagation.

Change-Id: I7fb4f054d53fe9ae4e0c4e395a0e6f51c50d3403

… integration

- Introduces `SAPKMSCryptoPlugin`, a Fernet-based crypto engine compatible with Barbican’s upstream plugin interface.
- Adds `PerSecretKEKStoreAdapter`, enabling per-secret KEK resolution via user metadata (`sap_gtid`).
- Replaces legacy ToyCryptoPlugin references with SAPKMS equivalents.
- Updates `setup.cfg` entry points and `barbican.conf` to register `sap_kms_crypto` and `sap_kms_adapter`.
- Ensures full compatibility with upstream Barbican `cbase` DTOs and plugin manager.
- Includes improved logging, safe key handling, and transient plugin_meta propagation.

Change-Id: I7fb4f054d53fe9ae4e0c4e395a0e6f51c50d3403
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant