Cryptographic service provider api with non-native key emulation

A computer system comprising:

• one or more processors;
• one or more computer-readable storage media;
• and
• program instructions stored on the one or more storage media to cause the one or more processors to perform operations comprising:
• parsing, by a first cryptographic service provider (CSP) application interface (API), a full cryptographic key token from a second CSP API, into a functional key object and a non-functional metadata object;
• cryptographically linking the functional key object and the non-functional metadata object to form a linked object pair representing the full cryptographic key token;
• in response to a CSP API call, generating an updated cryptographically linked object pair by updating at least one of either the cryptographically linked functional key object or the non-functional metadata object of the linked object pair;
• and
• exporting, by the first CSP API, a fully formed modified cryptographic key token based on the updated cryptographically linked object pair.

A computer program product comprising:

• one or more computer-readable storage media;
• and
• program instructions stored on the one or more storage media to perform operations comprising:
• parsing, by a first cryptographic service provider (CSP) application interface (API), a full cryptographic key token from a second CSP API, into a functional key object and a non-functional metadata object;
• cryptographically linking the functional key object and the metadata object to form a linked object pair representing the full cryptographic key token;
• in response to a CSP API call, generating an updated cryptographically linked object pair by updating at least one of either the cryptographically linked functional key object or the non-functional metadata object of the linked object pair;
• and
• exporting, by the first CSP API, a fully formed modified cryptographic key token based on the updated cryptographically linked object pair.