Kibo for Java changelog
Release notes for dev.k9o:kibo, from the CHANGELOG.md in the sdk-kibo-java repository. Read on 17 November 2026 at 15:55 UTC.
1.5.2
Changed
- README: Architecture at a glance, illustrations, and the package table lists only the packages for that SDK.
1.5.0
Added
-
KiboClientCore, the client core fork9o.crypto()on a BYOK or HYOK project: opens and seals on this machine against your own KMS or HSM. It takes a federated token, exchanges it for a credential on your cloud, then seals or opens through the bound core (kibo-kms-rest-ffi 2.15.0 or later, reached through the newAppCoreinterface). Key, provider, region, role and endpoint come from your configuration only.expectedKeyRefsis required and non-empty, and the configured key must be in it; an empty list from the router is refused before any network call. A core that does not declareexpected_key_refsis refused withK9O_CRYPTO_KEY_PIN_UNENFORCED, and a core without the new functions withKIBO_WASM_ERROR. A token response naming anotherproviderorprojectIdis refused withK9O_INVALID_FIELD_VALUE. The exchange has a deadline (default 30 s,KIBO_EXCHANGE_TIMEOUT); the credential is cached per crypt, op and subject until 60 s before it expires. No token or credential appears in an error ortoString. Item failures carry the core's code. -
UniffiAppCore, a ready adapter that runsKiboClientCoreover the generated Kibo core binding, so you no longer write your own. It converts the SDK's values to the binding's types and turns the core's errors into"<CODE>: <detail>"(UPSTREAM_KMS_ERRORfor your KMS's refusals). It is compiled when the binding is insrc/main/kotlin(profilewith-binding); without the binding the module still builds its pure-Java part (profileno-binding).
Changed
-
The Vault federation spec field
mountis nowjwtAuthMount(AppCore.FederationSpec.Vault). It is the JWT auth mount: the name Vault serves the JWT login under,jwtforauth/jwt(not the transit mount, which comes from the key reference). -
A call whose own
expectedKeyRefsdoes not contain the configured key is refused per item withK9O_CRYPTO_UNEXPECTED_KEYbefore the federated token is fetched and before the cloud exchange (it was only refused later, inside seal/open). -
Depends on
dev.k9o:core1.5.0 (forCrypto.ClientCore). -
README description.