Strong Authentication provides the following authentication methods out-of-the-box:
CA AuthID is a CA-proprietary secure software credential that provides two-factor authentication. The CA AuthID is a small data file that by itself can be used for strong authentication to a variety of clients such as, Web or Virtual Private Networks (VPNs).
See "CA AuthID Key Concepts" for more information about CA AuthID.
A regular credential, where the user is issued a username and a password to log in to the system.
One-time password is another credential generated by Strong Authentication Server. An OTP/Activation Code can be numeric or an alpha-numeric string. It is also possible to configure the number of times it can be used.
One-time passwords that are complaint to Open Authentication (OATH) standards. Strong Authentication supports both counter-based OATH OTP/Activation Codes (HOTPs) and time-based OATH OTP Tokens (TOTPs).
Question and Answer (also known as QnA) is a challenge-response authentication mechanism. Users authenticate to Strong Authentication Server by providing correct answers for the questions they are asked. These Questions and Answers are set by the users themselves during registration.
CA AuthID OTP is compliant to the OATH, Europay, MasterCard, and VISA (EMV) standards. If your application is integrated with CA AuthID OTP, then it accepts the user’s password as an input and generates passwords (also known as passcodes) on the users’ device. The user, then, submits this generated passcode to authenticate to your Web application. Based on the authentication result, the user is granted access to the protected application or denied access.
Passcode generation is an offline process, which means that your application need not be connected to Strong Authentication for generating passcodes.
Strong Authentication supports LDAP authentication, where the user credentials in the directory service are used to authenticate users.
You can issue one or more of these credentials to your users. You can also issue multiple credentials of the same type. For example, you can issue two password credentials, an CA AuthID credential, and a QnA credential for a single user.
If you want to extend the default authentication mechanisms, then Strong Authentication provides you the flexibility to do so by writing Plug-Ins.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|