Skip to main content
Do this when your own rules ask for new keys from time to time. A new key does not turn off the old one, as the last section says.

Before you start

  • A role in Casefile that may make keys, such as admin.
  • Access to where the sending system keeps its key, such as a secret store.

Steps

1

Make a new key

In Casefile, open the organization menu, then Settings, then Sources and keys. Enter the system’s source name, choose Make a key, and copy the key. It is shown only once. A key works for every source in your organization, so the name only fills in the command on the screen.
2

Try the new key

Put the new key in CASEFILE_KEY and send one event.
The door answers 202 with your event’s ID in accepted.The door can refuse a new key with unknown key for up to 5 seconds after it is made. If it does, send the same event again.
3

Give the system the new key

Replace the old key where the system reads it, then restart or redeploy the system so it reads the new one. Events it sends with the old key in the meantime are still accepted, so none are lost.
The new key got 202 from the door, and Data health shows the system’s events arriving after its restart.

The old key

The app cannot turn off a door key, so the old key keeps working. Keep it as secret as the new one.