Red Hat Single Sign-On Administration (DO313) — Lesson 3: Identity Brokering, LDAP Federation, Mappers, Authentication, and Authorization

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing identity brokering and LDAP federation.
• Implement and validate mappers, authentication flows, and authorization services using reviewable evidence.
• Evaluate the condition where operators cannot explain the outcome because logs, commands, settings, and acceptance evidence were not captured consistently and select a proportionate corrective response.

Detailed Topics

• identity brokering applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• LDAP federation applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• mappers applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• authentication flows applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• authorization services applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an identity team centralizing authentication and federation for enterprise applications and OpenShift-hosted services. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the single sign-on realm design, client integration records, federation evidence, and identity operations runbook. It also tests the exception where operators cannot explain the outcome because logs, commands, settings, and acceptance evidence were not captured consistently.

Hands-On Exercise

Complete a controlled Red Hat exercise covering Identity Brokering, LDAP Federation, Mappers, Authentication, and Authorization and preserve the verified result in the single sign-on realm design, client integration records, federation evidence, and identity operations runbook.

1. Confirm scope, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording commands, settings, outputs, events, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, rollback, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences identity brokering.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the single sign-on realm design, client integration records, federation evidence, and identity operations runbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check prerequisites, identity, configuration order, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “operators cannot explain the outcome because logs, commands, settings, and acceptance evidence were not captured consistently” as a hypothesis until commands, logs, settings, and retest outcomes confirm the cause.

Validation Checklist

• Required platform components, identities, permissions, settings, and dependencies are present.
• The single sign-on realm design, client integration records, federation evidence, and identity operations runbook connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Identity Brokering, LDAP Federation, Mappers, Authentication, and Authorization, explain the resulting platform behavior, and defend the outcome through the single sign-on realm design, client integration records, federation evidence, and identity operations runbook.