Introduction
Overview
This section describes the Control Center view when it is configured for the first time.
Terms
| Term | Description |
|---|---|
RP | A relying party (RP) is a term used to refer to a server providing access to a secure software application. |
RP App | Claims-Based applications, where a claim is a statement an entity makes about itself in order to establish access, are also called relying party (RP) applications. You can create multiple RP Apps to manage access to different systems within your infrastructure. |
Policy | Authentication Policy to access resources managed by RP App. Configured by Control Center Admin. |
AAID | Unique identifier for the Authenticator. |
Native Authenticator | Default Biometric Authenticator registered on the mobile device. It could be Touch ID or Face ID on iOS Platform, or Fingerprint, Face Authentication on Android Platform. |
PIN Authenticator | 6-Digit PIN specific to your Application. It's a separate Authenticator from device PIN and developed by HYPR. |
Login
Step 1: Open your browser and type in the DNS host name of your server: https://company.login.com. You should see the Control Center login page.
Step 2: Type in your HYPR Service Account username and password which was configured during installation. This credential is provided during the completion of the installation script.
The default username is hypr and password is listed in /opt/hypr/.install.enc file.
Step 3: Press Login
Encrypt file to access login credentials
Please decrypt the
.install.encfile to see the credentials of Control Center.
Dashboard
Below is the screen of the landing page of the Control Center upon a fresh install. The Dashboard contains the following attributes which can be managed by an admin:
There are two RP Apps created by default. Namely, 'HYPR Default Workstation Application' and 'HYPR Default Web Application'.
Please note
'HYPR Default Workstation Application' is used when the decentralized channel is workstation
'HYPR Default Web Application' is used when the decentralized channel is web.
Admins can create more RP Applications or can use the default applications to manage authentication across different resources within the company infrastructure.
Authenticators
Manage what authenticators can be used to authenticate into your application. See Managing Authentication Policies.
Policy Management
Manage authentication policies for your application. See Policy Management.
FIDO Registration
In this section you can see and manage registered FIDO Users.
User Management
Manage registered users and see information on their authentication history and access. See User Management.
Audit Trail
This section can be used to analyze user behavior and troubleshoot issues. See Audit Trail.
Workstation Settings
Manage Desktop MFA configuration. See Desktop MFA Settings.
Advanced Config
Access Tokens
Generate API Access Tokens in this section. This API token will be used to authenticate into the HYPR Server with HYPR APIs.
Push
In this section you can add Push Notification credentials. Please note that this is only needed for customers using the HYPR Mobile SDK.
FIDO FacetsID
In this section you can manage FIDO FacetsID. Please note that this is only needed if you are using the HYPR Mobile SDK.
UI Management
In this section you can manage the UI appearance of the mobile app to customize branding elements such as colors, company logo and support email.
IdP Management
Integrate with identity management providers (IdPs).
Extensions
Integrate with HYPR True Passwordless Extensions to extend the functionality of your authentication solutions. See Getting Started.
License Activation
In order to create more RP Applications, you must upload a valid license file. See License Key
SSL Pinning Configuration
Admins can upload certificates to enable SSL Pinning to enhance security. SSL Pinning can be enabled for mobile and desktop applications. Learn more about SSL Pinning in Deploy Desktop MFA: Deploying HYPR Manually on a Windows Workstation.
Updated 5 months ago