Notice that the user was logged into the Workspace ONE Access tenant without having to enter their credentials.  Upon logging in as holuser, the 3rd party Identity Provider you configured attempted to authenticate the user using Kerberos first.  After the Claim is processed in AD FS, the claim is transformed via the Claim Rules we created earlier and responds in a manner that Workspace ONE Access is able to process, thus authorizing the user to login using SAML.

1. Click the User dropdown.
2. Click Sign Out.

NOTE: Signing out may take several seconds to process from AD FS.  Please wait until you are taken back to the Workspace ONE Access login page.

This will clear the login cookie for the holuser.  The next exercise will showcase using the VMware Workspace ONE App to login, so the cookie needs to be cleared first.

1. Enter holuser for the username.  This is one of the corp.local domain users we synced.
2. Uncheck Remember this setting.
3. Click Next.

NOTE: The authentication process may take several seconds after clicking Next.  Please be patient and wait until the next page loads.

As seen in your browser session, the claim is transformed and the outgoing claim authorizes the user to access Workspace ONE via SAML without having to enter their credentials.

After successfully authenticating, you should see a message indicating that your workspace is being configured, and eventually that the workspace is ready.  

Click Enter.