VMware Workspace ONE: Integrations [V22.x] — Lesson 2: Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies

Learning Objectives

• Identify the architecture and operational choices that shape Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies.
• Run normal and boundary tests and record the outcome in identity synchronization report and access-policy test matrix.
• Separate root cause from symptom when investigating an attribute mapping placing users into the wrong entitlement group.

Detailed Topics

• Directory synchronization
• Identity sources
• User attributes
• Groups
• SAML
• OAuth
• Conditional access
• Device compliance
• Single sign-on
• And authentication policies
• Decision ownership, prerequisites, and acceptance evidence for Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies within a scenario aimed at a connected Workspace ONE environment that integrates identity, access, productivity services, mobile applications, directories, certificates, and endpoint compliance without weakening security boundaries. The walkthrough contrasts a valid setup with a flawed one and uses identity synchronization report and access-policy test matrix to make the difference explicit.

Hands-On Exercise

Configure and test Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies with representative infrastructure or application data. Use “an attribute mapping placing users into the wrong entitlement group” as the troubleshooting challenge, compare hypotheses, retest the affected path, and complete identity synchronization report and access-policy test matrix for review.

1. Confirm scope, access, sample workloads, and acceptance criteria.
2. Perform the configuration or operation using a controlled sequence.
3. Inspect outputs and downstream effects rather than relying on task status alone.
4. Close with a support note, preventive action, and reproducible validation step.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how identity synchronization report and access-policy test matrix should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect identity synchronization report and access-policy test matrix, test whether “an attribute mapping placing users into the wrong entitlement group” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• The scope of Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies is clear, including what is deliberately excluded from the test.
• Evidence in identity synchronization report and access-policy test matrix supports each material decision and outcome.
• A negative test demonstrates that controls reject or expose an invalid condition.
• Open risks, owners, due actions, and production safeguards are documented.

Lesson Outcome

Learners can apply Directory synchronization, identity sources, user attributes, groups, SAML, OAuth, conditional access, device compliance, single sign-on, and authentication policies, explain the decisions made, and defend the result with identity synchronization report and access-policy test matrix.