How to Govern and Maintain Compliance Using Open Source Identity Management Components
summary
midPoint (ASL 2.0) runs as a Java 8 webapp (Tomcat) with PostgreSQL and uses ConnId connectors to provision to real targets; the demo ingests an Oracle HCM XML file, imports a user named Larry, sends activation notifications (to file), enforces password policy, and creates accounts in Google Apps and OpenLDAP. The system enforces RBAC with static/dynamic separation, supports multi‑level approvals with a 1‑minute escalation, delegation/deputy, and runs access certification campaigns that push remediation to target resources.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 3:00Common Problems
- 6:32RoleBased Access Control
- 8:41Midpoint
- 12:05Other Users Accounts
- 12:30Demo Environment
- 16:56Use Cases
- 17:25Scenarios
- 18:17Scenario 1 Onboarding New Items
- 25:47Scenario 2 Requesting New Role
- 26:54Security Officer Approval
- 28:04Application Owner Approval
- 30:30Multilevel approval
- 32:09segregation of duty
- 34:43delegation
- 36:17certification campaign
- 39:46access certification
- 40:06benefits of governance
related talks
34mMidPoint - Open-Source Identity Management and Governance Platform
38mIdentity and Access Management in the 21st Century
12mIAM and Privileged Access Foundations for Secure ML Platforms
28mBuilding Identity for an Open Perimeter
35mIdentity and Access Management for the Decade Ahead
31mEnterprise Identity Management on Rails
16mThe Future of Identity Management: Transitioning from Operational to Intelligent Platforms
28mIdentity: From Legacy to Microservices