Integration ID

The Integration ID is a GUID (Globally Unique Identifier) that serves as the primary identifier for your Schlage integration when communicating with Allegion's API. This identifier represents a specific backend server or third-party system that communicates with our cloud infrastructure. The Integration ID is directly tied to your PACS (Physical Access Control System) or identity management system, establishing the foundational connection between your infrastructure and Allegion's platform.

A single Integration ID has the flexibility to support multiple mTLS certificates simultaneously, allowing for strong security configurations. Typically, one Integration ID supports all clients and applications that utilize the same backend Identity Management (IDM) system and JWT signing keys, creating a unified authentication framework.

When you need to integrate with a different backend server or use different IDM systems with separate JWT signing keys, a new Integration ID becomes necessary. However, multiple clients or Identity Providers (IDPs) can share the same Integration ID if they operate with identical IDM systems, audience settings, issuer configurations, and JWT signing keys, enabling efficient resource sharing and simplified management.

JWT Signing Key

The JWT (JSON Web Token) Signing Key maintains a one-to-one relationship with the Integration ID, ensuring secure and authenticated communication. This key is essential for the platform to validate JWT signatures, providing a secure method to verify the authenticity and integrity of tokens exchanged between your systems and Allegion's cloud infrastructure.

Completed Config Card

A completed config card is a physical plastic card that is shipped to your designated address. This card contains all the essential key information required for your integration setup, serving as a tangible record of your configuration details and providing a backup reference for your integration parameters.

Client Configuration

Client Configuration typically represents a specific site or location and exists within a single Integration ID. This configuration allows for multiple clients with different Identity Providers (IDPs) or audience claims to be supported by creating separate integrations as needed. The client configuration provides the flexibility to manage different access requirements and authentication methods while maintaining centralized control under your Integration ID.

Client ID

The Client ID is a GUID that represents your specific application when making API calls to Allegion. This identifier allows the platform to distinguish between different applications and manage their respective permissions and configurations. The relationship between clients and integrations follows a flexible model where clients can have a one-to-one relationship with integrations, while integrations can have a one-to-many relationship with clients, providing scalability and organizational flexibility for complex enterprise environments.