About Passlock tenancies

Your Passlock cloud account includes multiple “tenancies”. Each tenancy is fully isolated. Tenancies are identified by a tenancyId. Each tenancy has its own data, including API Key(s).

The Development Tenancy

Each Passlock cloud account includes Development, Staging and Production tenancies. Staging and Production have identical characteristics, but the Development tenancy has some unique characteristic,which improve the developer experience.

Danger

Do not use your Development tenancy for production data. If stable identifiers are enabled (see below) an attacker could substitute a passkey in your vault with their own.

Stable credential IDs

During development you’ll likely register passkeys with the same username over and over again. By default, your browser will generate a new passkey each time. You’ll end up with multiple passkeys for the same username in both your vault and local passkey manager.

To prevent this happening, you need to use the excludeCredentials property, along with some checks in your backend code. You should do this in production.

To make the developer’s life easier we use stable credential IDs in Development. This means a new passkey with the username jdoe@example.com will overwrite the existing jdoe@example.com passkey in both the backend vault, and device passkey manager. You can continue registering passkeys without accumulating duplicates.

Disabling stable IDs

When you’ve got the basics out of the way, go into your Development tenancy settings and disable stable identifiers. Passkey registration will then behave as it does in Staging and Production.

Logging

Each tenancy features isolated logging. Logs can be viewewd in your console, and soon via the REST API. We create more log entries in the Development tenancy:

1. Development - DEBUG INFO WARN ERROR
2. Staging - INFO WARN ERROR
3. Production - WARN ERROR