User's Guide
authentication or SSO). For example, you might have one identity (me@company.com) from when
the org was created (under the local org namespace) that is authenticated through email and
password. If you sync with an identity provider that has the same email (me@company.com) in it,
another identity will be created under the identity provider namespace.
Identities are separate from, but related to users. A user is an instance of an identity that belongs
to a specific org, so a single identity could have multiple users. This model allows a single identity
(email and password) to be able to access multiple orgs, which is useful for resellers and installers
that need to be able to log in once but have access to many orgs. Identities are what let you log into
the Control Center; users are where you configure portal access, roles, and Entry access for a
particular org.
CONFIGURING OPENPATH WITH LEGACY SYSTEMS
You can configure Openpath to support existing legacy access control systems. In this setup,
Openpath Smart Readers replace the legacy Wiegand readers and Openpath Smart Hub ACUs are
installed between the Smart Readers and the legacy panel, with the Wiegand ports configured as
outputs to the legacy panel. In this setup, the legacy panel makes the access control decisions
while the Openpath hardware allows the use of Openpath credentials (including mobile and cloud
key credentials).
Version 1.9
©
Openpath 2019
Page 41