#1155 archive_encrypted_data() should not require base-64 encoded parameter
Closed: Fixed None Opened 9 years ago by edewata.

Currently the archive_encrypted_data() method in KeyClient requires the symkey_params to be base-64 encoded, which requires an additional step in the caller's code.

nonce_iv = generate_nonce_iv()
algorithm_oid = KeyClient.DES_EDE3_CBC_OID
symkey_params = base64.encodestring(nonce_iv)

key_id = key_client.archive_encrypted_data(
    client_key_id,
    data_type,
    wrapped_private_data,
    wrapped_session_key,
    algorithm_oid,
    symkey_params,
    key_algorithm,
    key_size)

To make the API more developer-friendly, the method should perform the encoding internally:

nonce_iv = generate_nonce_iv()
algorithm_oid = KeyClient.DES_EDE3_CBC_OID

key_id = key_client.archive_encrypted_data(
    client_key_id,
    data_type,
    wrapped_private_data,
    wrapped_session_key,
    algorithm_oid,
    nonce_iv,
    key_algorithm,
    key_size)

Base-64 encoding should only be needed to marshal the data into JSON.


Per Dogtag 10.2.3 Triage meeting of 09/24/2014 - proposed Milestone: 10.2.1

NOTE: edewata and vakwetu to discuss

master: cfeb77bb5d79f0e131948e864a1dcba2451758f6

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.1

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1718

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata