get_policy: Retrieve the policy for a certificate.set_policy: Sets the policy for a certificate, ie the authentication details.verify: Verify a signature against a digest.export_cer: Export the certificate public key as a CER file.export: Export the certificate as either a PEM or PFX file (the format is fixed at certificate creation).The default is to use the most recently created version. set_version: Set the version of the certificate to use.

list_versions: List the available versions for this certificate.Used by the above methods.ДЄn individual certificate is represented by an object of class stored_certificate. do_operation: Carry out arbitrary REST operations on certificates.list_issuers: Lists the issuers available to this vault.remove_issuer: Removes the details for an issuer.get_issuer: Retrieve the details for an issuer.add_issuer: Adds the details for an issuer (certificate authority).get_contacts: Get the email address(es) of the contacts.set_contacts: Set the email address(es) to contact when a certificate is due for renewal.restore: Use a blob obtained by the backup method to restore a certificate.backup: Return a base64-encoded blob representing the certificate.list: List all certificates in the vault.import: Import a certificate from a PFX file.The default is to create a self-signed certificate. create: Create a new certificate, or a new version of an existing certificate.The certificates component provides methods for working with SSL/TLS authentication certificates: If you want the raw string value itself, eg when passing it to jsonlite::toJSON or other functions which do not accept arbitrary object classes as inputs, use unclass to strip the class attribute first. Note that this will not stop a determined attacker as a general rule, you should minimise assigning secrets or passing them around your R environment. This class has a print method that hides the value, to help guard against shoulder-surfing. The secret itself is in the value field of the object, of class secret_value. set_version: Set the version of the secret to use.list_versions: List the available versions for this secret.It has the following methods for managing secret versions: Unlike a key, a secret is essentially just data, so the object does not provide any operations.

Used by the above methods.ДЄn individual secret is represented by an object of class stored_secret.

do_operation: Carry out arbitrary REST operations on secrets.

restore: Use a blob obtained by the backup method to restore a secret.

backup: Return a base64-encoded blob representing the secret.

create: Create a new secret, or a new version of an existing secret.

The secrets component of the client object provides methods for managing generic secrets: Key Vault allows you to store confidential information such as passwords, database connection strings, tokens, API keys, and so on. Note that Azure Key Vault does not provide access to the private key component. The key object contains the public key component in the key field, as a parsed JSON web key. This is technically the same as encrypting it, but is provided as a distinct operation to allow more granular management of permissions.

verify: Verify the signature of a hash.

decrypt: Decrypt a ciphertext string, producing either a character string or raw vector.

encrypt: Encrypt a character string or raw vector, producing a base64-encoded ciphertext string.

set_version: Set the version of the key to use.

list_versions: List the available versions for this key.

In turn, an individual key is represented by an object of class stored_key.

do_operation: Carry out arbitrary REST operations on keys.

restore: Use a blob obtained by the backup method to restore a key.

backup: Return a base64-encoded blob representing the key.

create: Create a new key, or a new version of an existing key.

The keys component of the client object provides methods for managing keys: Key Vault supports RSA and elliptic curve (ECDSA) asymmetric encryption keys.

Key vault password manager