This page contains a list of possible scenarios where Indeed AM components may be used. To implement different system scenarios, you need to install various client components. Server-side components − Indeed AM server, Indeed Admin Console, and Indeed AM Log Server must be pre-installed for all scenarios


Strong authentication for domain PC connections inside your corporate network 

This scenario is supported by the Indeed AM Windows Logon component. This component enables strong authentication for system connections and relies on various authentication methods, including biometric authentication, contactless RFID cards, USB keys, contact smart cards, one-time passwords, and push notifications in the mobile app. 

All supported authentication methods are listed in the section Installation and configuration of providers.

Strong authentication for target web/Windows applications 

This scenario is supported by the Indeed AM ESSO Agent component. It is based on the Single Sign On access technology designed for connections to corporate information systems. It offers centralized app password storage and automatic entry of hidden passwords during login or other operations that require the use of various authentication methods, including biometric authentication, contactless RFID cards, USB keys, contact smart cards, one-time passwords, and push notifications in the mobile app. 

All supported authentication methods are listed in the section Installation and configuration of providers.

Two-factor/One-factor authentication for VPN connections

The Indeed AM NPS RADIUS Extension component can be used for scenarios that require VPN client support. This component enables two-factor/one-factor authentication for services and applications compatible with the RADIUS protocol. It supports different types of user authentication, such as one-time passwords sent via SMS or by email, one-time passwords generated by special devices, and push notifications. 

Two-factor authentication for RDP connections

The Indeed AM RDP Windows Logon component can be used for RDP connections via 2FA. 

Master passwords (passcode provider), one-time passwords generated by a mobile app (software OTP provider) or device, one-time passwords sent via SMS or by email, or push notifications can be used as a second factor. 

Two-factor authentication for apps supporting ADFS

This scenario is supported by the Indeed AM ADFS Extension component. Multi-factor authentication provider for Microsoft ADFS server deploys the ADFS Extension component and adds a second factor during login. 

Master passwords (passcode provider), one-time passwords generated by a mobile app (software OTP provider) or device, one-time passwords sent via SMS or by email, or push notifications can be used as a second factor.

Two-factor authentication for applications supporting SAML

This scenario is supported by the Indeed AM SAML idp component. 

Master passwords (passcode provider), one-time passwords generated by a mobile app (software OTP provider) or device, one-time passwords sent via SMS or by email, or push notifications can be used as a second factor.


  • No labels