Build your api credential rotation planner.

How to build your api credential rotation planner

1. 1

   Describe the job

   Track credential rotation tasks without storing the secret values in the planner.

2. 2

   Review the first version

   Choose how the it administrator records the credential reference and how the system owner reviews the next step.

3. 3

   Refine the views

   Ask First to adjust the fields and views for the people who will use the app.

4. 4

   Test before sharing

   Walk through the process with a sample record and check who owns the next action.

What to include in your api credential rotation planner

• Keep the credential reference in context

  Keep credential reference, owner, system, rotation due, test evidence and revocation confirmation together so the next person can understand the request or record.

• When the next step needs a decision

  A new credential is configured but the previous one is not yet confirmed revoked. Keep the two completion steps separate and never store the secret value in the planner.

• Keep revocation confirmation visible

  Keep the old credential's revocation outstanding until its owner confirms it.

• Choose what each person needs

  Give the it administrator a working view and the system owner a review view. Keep credential reference and owner attached to the decision as the work moves between them.