Skip to main content

View credential history

Why track credential history?

Tracking the history of a credential is important for:

  • Auditing: Monitor who created, updated, or issued a credential, and track any changes made.
  • Compliance: Ensure compliance with regulatory requirements by maintaining a complete record of a credential's lifecycle.
  • Data Integrity: Validate that a credential has not been tampered with or altered without authorization.

Example: View credential history

To view the history of a credential, use the credentialHistory method:

await client.credentials.credentialHistory("id", {
ifNoneMatch: "5db68c06-1a68-11e9-8341-68f728c1ba70"
});

Where ifNoneMatch declares a list of identifiers required to fail matching all the current resource version identifiers as a pre-condition for executing the request on the server side. This is especially used in conjunction with an * (asterisk) that matches all possible resource identifiers to ensure the initial creation of a resource.