Part III Performing Device Authentication with Oracle Universal Authenticator

Once the Oracle Universal Authenticator client application is installed, the end user can log into Microsoft Windows using the Oracle Universal Authenticator option.

When the Oracle Universal Authenticator login is selected for the first time, the user is required to enter both their Oracle Access Management (OAM) credentials and their Windows credentials, and any second factor credentials previously configured. This is required so Oracle Universal Authenticator can configure the tokens it needs for successful operation.

Note:

Before using Oracle Universal Authenticator, users must have at least one factor configured in the Self-Service Portal:

• Administrators should refer to the following documentation for onboarding users and their factors: Onboarding Users
• Users can manage their factors using the Self-Service Portal: Managing Factors in the Self-Service Portal

Once the initial logins are successful and the user and device is registered, the user can login to OAM protected applications and Windows applications without the need to enter any further credentials.

For any subsequent Windows login, if the same user selects to login with Oracle Universal Authenticator, the user will only be asked to enter their OAM credentials, and a second factor credential. Once logged in, the user can login to OAM protected applications and Windows applications without the need to enter any further credentials.

This chapter contains the following topics:

• First time login to Microsoft Windows with OUA
• Subsequent login to Microsoft Windows with OUA
• Accessing Applications Protected with SSO
• Offline Login

Note:

For more detailed information and step by step tutorials, see Usecases.