Authentication Service
Cost-efficient and user-friendly multi-factor authentication
Mideye offers cost-efficient and user-friendly authentication of remote users, primarily utilizing the mobile phone as the second layer of security.
The Mideye Service comprises two main components: a general-purpose authentication engine (Mideye Server) and a central cloud-based authentication service. The Mideye Server is installed at customer premises and acts as a back-end RADIUS server for access products such as VPNs, firewalls, portals and cloud applications (see our list of verified integrations). To minimize the provisioning and administrative burden, the Mideye Server can read user data from existing LDAP repositories (e.g. Active Directory) without requiring any schema changes.
The Mideye Server connects to the central authentication service via a secured internet connection. The cloud service includes an OTP (one-time password) delivery service, provisioning and life-cycle management of apps for smartphone users, as well as a token management and logistics service for users that cannot use a mobile phone for login.
Login Modes
The following login modes are supported:
SMS-OTP
For users with GSM/3G/4G compliant phones, Mideye offers login with OTPs delivered in real-time via the mobile network. The Mideye Services maintains dedicated direct connections to leading mobile operators for optimal performance, reliability and redundancy. View our global coverage.
APP-OTP
For users with smartphones (Android and iPhone), the Mideye+ solution offers login also when outside of network coverage. The central service includes app provisioning and life-cycle management. Smartphone users can opt to activate and de-activate Mideye+ at their own discretion without requiring any additional provisioning in the user repository.
Token-OTP
As an alternative to the mobile phone, authentication with OTPs from token cards is fully integrated in the Mideye Service. Token cards are shipped to end-users world-wide, and only the corresponding token serial number is required in the user repository.