Encryption
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
The request body can contain an array of Encryption Requests to support bulk encryption. The key for encryption will be decided based on the tenantId. Each tenant will have its own seperate key. The value to be encrypted can be simple string OR an array of string OR can be a JSON Object. In case the value is a JSON Object, all the values will get encrypted and keys will be left untouched.
The returned encrypted value will have the same structure as the input value.
Input to a decryption request may be an simple string OR an array OR a JSON Object. Every Object/Array will be navigated through to find simple strings, and those strings will be decrypted.
The response to a decryption request will have the same structure as the input.
Request contains tenant id and the value that needs to be signed.
The key used for signing will be determined based on tenant id.
The value to be signed.
Response contains the value that has been signed and the value of signature.
The value that came with request.
The signature generated for the above value.
Request contains the value and its signature.
The claim to be verified
The signature for the claim
Response returns if the provided signature is correct for the given value.
This will be true if the signature is correct according to the claim, otherwise false.
Request has the name of the tenant for which the key needs to be rotated.
The tenantId for which the key needs to be changed.
Acknowldgement if the operation was successful.
Acknowledgement if the operation was successful.