Using machine authenticators

The process of authentication attempts to establish trust by authorizing a trusted source, such as a user. In the case of machine authentication, the trusted source is a client, such as your desktop computer. For example, when you use a Web browser on your desktop computer to authenticate, it generates a machine secret. When you authenticate, machine authentication submits the current machine secret to Identity as a Service and compares it to a previously stored machine secret. If the machine secret from your Web browser matches the machine secret stored in IDaaS, the authentication risk is lower. If it does not match, the risk is higher. 

Depending on how your administrator has defined the resource rule that protects the application you are trying to access, a matching machine secret (lower risk) might require lower authentication (for example, first-factor without second-factor) to access the application. If the machine secret does not match, a higher level of authentication is likely required (for example, both first-factor and second-factor).

You can create machine secret by either activating a machine authenticator when you log in to IDaaS or assign one in IDaaS. When you assign a machine authenticator in IDaaS, IDaaS creates the machine secret the first time you log in to the protected application.

Choose one of the following procedures, as required:

Activate a machine authenticator during login

Assign a machine authenticator from your My Profile page