Requesting a new client when you have an existing implementation

Last modified: 01.11.2025

Preface

 

Understanding the mapping of clients and integrations is essential when reviewing this guide. Integrations follow a one-to-many relationship with clients, though a many-to-many relationship is also supported (though not recommended). Allegion supports:

 

One integration → Many clients

 

One Client → One integration

 

Each client can have its own integration, but a client can only be associated with one integration at a time. When requesting a new NFC client (typically mapped to a site) within the mobile credentials product, all previously provided information can remain the same, or it can change—depending on your needs. However, Allegion needs to know what you intend to keep and what you plan to modify. This guide outlines which elements are reusable and which require updates so you can communicate your requirements effectively.

Configuration Considerations

Webhook Delivery Endpoint (Client Level - Reusable)

• If you want to receive webhooks from all clients at the same endpoint, no changes are needed.
• If you require separate webhook endpoints for different clients, provide Allegion with the specific endpoint where you want to receive events.

mTLS Certificate (Implementation Level - Reusable)

• Allegion supports multiple mTLS certificates for your integration simultaneously.
• A single mTLS certificate can be used across your implementation.
• If your implementation makes requests to Allegion using multiple mTLS certificates, you must provide all of them.

Firewall Headers (Client Level - Reusable)

• If your implementation requires headers to bypass a firewall and receive events, you must provide these headers to Allegion.
• These headers can be reused across multiple clients.

Access/ID PEM (Integration Level - Reusable)

• These PEM files are public keys used to verify the signatures of ID and Access JWTs sent to Allegion.
• Allegion can validate these using either a single key for both ID and Access JWTs or separate keys for each.
• If all clients are mapped to a single integration, no changes are needed.
• If different keys are required for certain clients, a new integration must be created, and the corresponding keys provided.
• Important: An integration supports only one set of keys at a time—multiple ID or Access PEMs cannot be mapped to the same integration.

Card Art (Client Level - Reusable)

• Allegion supports per-client card art configurations.
• Each site can have unique card art, but this is optional.
• iOS and Android card art packs can be generic or customized for specific clients.
• Any combination is supported (e.g., 9 clients using the same generic card art pack while 1 client has a custom pack).