Credentials and Check connection

The Credentials screen holds the keys that secure the link between NetApps InsureTech and your middleware (your API or the adapter Adapter AI built). Use it to issue and rotate keys, paste them into your middleware, and prove the link works with Check connection.

How the link is securedlink

• Requests to you. NetApps InsureTech signs every request to your middleware with an API key and a signing secret, identified by a key id. Your middleware checks them.
• Webhooks to us. Your middleware signs the events it sends to NetApps InsureTech with a separate webhook secret, and sends them to your inbound webhook URL.

Who can do whatlink

Only an owner can issue, rotate or revoke keys, finish a rotation, run Check connection and regenerate the webhook URL. Everyone else sees the keys with masked values and the last results, with the note "Only an owner can issue, rotate or revoke keys and run Check connection."

Choose an environmentlink

Use the Environment list at the top of Keys. Sandbox is always available. Production appears once your company is Certifying or Live. Until then the screen says "Production keys become available once the provider is certifying. Sandbox keys are available now."

Issue credentialslink

1. Choose the environment.
2. Select Issue credentials.
3. In Copy these values now, select the copy button next to the environment block.
4. Store the block somewhere safe, tick "I have copied and securely stored these values." and select Done.
5. Paste the block into your middleware's settings and restart every copy of it.
6. Run Check connection.

The environment block sets these variables. Each OIIS_KEY_IDS, OIIS_API_KEYS and OIIS_SIGNING_SECRETS value is a comma-separated list, so your middleware can accept two keys during a rotation.

OIIS_KEY_IDS=
OIIS_API_KEYS=
OIIS_SIGNING_SECRETS=
OIIS_WEBHOOK_URL=
OIIS_WEBHOOK_KEY_ID=
OIIS_WEBHOOK_SECRET=

Read the key listlink

The list has two sections: API key and signing secret, and Webhook secret. Each row shows the key id, the masked value, when it expires (or Stops working, for a retiring key) and when it was last used.

API keys last 24 months. Signing secrets and webhook secrets last 12 months.

Rotate without downtimelink

API key and signing secretlink

1. Select Rotate in API key and signing secret. A new key appears as New, waiting, and the environment block opens with both the current and the new key.
2. Paste the new block into your middleware and restart every copy.
3. Run Check connection. When it passes with the new key, NetApps InsureTech switches to it and the result says "We now sign with key …".
4. The old key shows Retiring and stops working after 7 days. To stop it sooner, select Finish now.

Webhook secretlink

1. Select Rotate in Webhook secret. The new secret appears as New, waiting, and the environment block opens with it.
2. Put the new OIIS_WEBHOOK_KEY_ID and OIIS_WEBHOOK_SECRET in your middleware.
3. NetApps InsureTech switches on the first webhook signed with the new secret. To switch at once, select Finish now, then Switch now. From then on, webhooks signed with the old secret are refused.
4. The old secret retires. Select Finish now, then Stop now to stop accepting it straight away.

Rotate stays disabled while a rotation is in progress.

Revoke a keylink

Select Revoke on a key's row, then Revoke now. The key stops working within 30 seconds on every NetApps InsureTech server.

Inbound webhook URLlink

Your middleware sends its events to this URL. It is shown once, in the environment block. Afterwards the screen only shows how it ends.

To replace it, select Regenerate webhook URL, then Regenerate. The new URL is shown once. The current URL keeps working for 7 days. If you regenerated within the last 7 days, the oldest URL stops working at once. Update OIIS_WEBHOOK_URL in your sandbox and production middleware.

Check connectionlink

Select Check connection in the Check connection card. It takes up to a minute and runs four steps:

Each step shows Passed, Failed or Skipped, with a fix when it fails. The Troubleshooting guide lists every fix.

Only one check runs per environment at a time. After you go live, NetApps InsureTech also checks production every 15 minutes. See Health and alerts.