Keymanager

Key specifications Soliton KeyManagerPlatform: WindowsOperating system version: Windows 11 (Except on ARM) / Windows 10 (Except on ARM)Platform: Mac OSOperating system version: 15/14 / 13* From macOS 11 or later, manual installing downloaded mobileconfig to [Setting] - [Profile] is required.* From macOS 13 or later, using the "Keychain Access" application to enable TLS trust for installed CA certificates is required.Platform: iOSOperating system version: 18.3-18.0 / 17.7-17.0 / 16.7-16.0Platform: iPadOSOperating system version: 18.3-18.0 / 17.7-17.0 / 16.7-16.1 Platform: AndroidOperating system version: 15.0 / 14.0 / 13.0 / 12.0 / 11.0Download information Soliton KeyManagerPlatform: WindowsUpdated: February 27, 2025Version: 2.2.1Size: 16.2MBSHA256：B593D84F0559A4F2499DF666B565D0236C4C43826D5CAB94530B0A105AEA3F91Update Procedure to V2.0.4 or later:In case updating from V2.0.0 ～ V2.0.2, please make sure to update to V2.0.3 and then update to V2.0.4 or laterDownload Soliton KeyManager V2.2.1 WindowsWhat’s New:Fixed bug that some communication does not go through proxy server.Platform: WindowsVersion: 2.0.3Size: 11MBSHA256：206319A2802AE1C57A1DA7A14778D70933689CF00675F0C4A2F8B0FF69559AE9Notice：V2.0.3 is only for update to V2.0.4 or later from V2.0.0 ~ 2.0.2.Download Soliton KeyManager V2.0.3 WindowsPlatform: macOSUpdated: March 12, 2025Version: 2.0.9Size: 5.3MBSHA256：61efb285f3ffecc440eed96b2d4c7b3cf07fbee0ef15b34e6411b2e5c46c0d6cDownload Soliton KeyManager V2.0.9 for MacOSWHAT’S NEW：Fixed a bug that occurred in macOS 15Platform: iOSThe application can be downloaded from the App StorePlatform: AndroidThe application can be downloaded from Google Play

Needed KeyManager-instances manually.For a concrete example, let‘s assume that we’d like a custom implementation of the Aead primitive (step #1). We define then three protocol buffer messages (step #2):MyCustomAeadParams: holds parameters needed for the use of the key material.MyCustomAeadKey: holds the actual key material and parameters needed for its use.MyCustomAeadKeyFormat: holds parameters needed for generation of a new MyCustomAeadKey-key. syntax = "proto3"; package mycompany.mypackage; message MyCustomAeadParams { uint32 iv_size = 1; // size of initialization vector in bytes } message MyCustomAeadKeyFormat { MyCustomAeadParams params = 1; uint32 key_size = 2; // key size in bytes } // key_type: type.googleapis.com/mycompany.mypackage.MyCustomAeadKey message MyCustomAeadKey { uint32 version = 1; MyCustomAeadParams params = 2; bytes key_value = 3; // the actual key material }The corresponding key type in Java is defined as String keyType = "type.googleapis.com/mycompany.mypackage.MyCustomAeadKey";`and the corresponding key manager implements (step #3) the interface KeyManager class MyCustomAeadKeyManager implements KeyManagerAead> { // ... }After registering MyCustomAeadKeyManager with the Registry, it will be used when you call keysetHandle.getPrimitive(Aead.class).

Primitive from step #1 and the key type from step #2.To use a custom implementation of a primitive in an application, register with the Registry the custom KeyManager implementation (from step #3 above) for the custom key type (from step #2 above): Registry.registerKeyManager(keyManager);Afterwards the implementation will be accessed automatically by the keysetHandle.getPrimitive corresponding to the primitive (when keys of the specific key type are in use). It can also be retrieved directly via Registry.getKeyManager(keyType).When defining the protocol buffers for the key material and parameters (step #2 above), you should provide definitions of three messages:...Params: parameters of an instantiation of the primitive, needed when a key is being used....Key: the actual key proto, contains the key material and the corresponding ...Params proto....KeyFormat: parameters needed to generate a new key.Here are a few conventions/recommendations when defining these messages (see tink.proto and definitions of existing key types for details):...Key should contain a version field (a monotonic counter, uint32 version;), which identifies the version of implementation that can work with this key....Params should be a field of ...Key, as by definition ...Params contains parameters needed when the key is being used....Params should be also a field of ...KeyFormat, so that given ...KeyFormat one has all information it needs to generate a new ...Key message.Alternatively, depending on the use case requirements, you can skip step #2 entirely and re-use an existing protocol buffer messages for the key material. In such a case, you should not configure the Registry via the Config-class, but rather register the