Configured connector paths around CSV, LDAP, and SQL-style resources so the project moved beyond a single-source demo.
IAM Lab with midPoint Connectors
Academic IAM project centered on midPoint, connector configuration, provisioning flows, workflow logic, and reproducible step-by-step documentation.
Key highlights
- Worked through dense IAM documentation and turned it into a reproducible configuration path.
- Focused on connector behavior, mappings, and provisioning logic instead of treating IAM as a black box.
- Documentation became part of the technical work so the lab could be handed over and reused.
ContextAcademic identity and provisioning lab
Core focusConnectors, mappings, provisioning, and workflow validation
Data pathsCSV, LDAP, and SQL resources around midPoint
What I handled
Worked on schema handling, inbound or outbound mappings, and the logic required for identities to propagate correctly.
Tested the resource behavior step by step, noted where provisioning or workflow assumptions broke, and documented the recovery path.
Built tutorial-style documentation with commands, UI actions, and observed results so the lab could be reproduced later.
Results & evidence
Connector architecture
Timeline
Initial connector setup
Configure the first resource path, validate import behavior, and understand how data enters midPoint.
Mappings and propagation
Work on schema handling, inbound or outbound mappings, and resource-side propagation logic.
Multi-resource IAM case
Expand the lab around LDAP and SQL style resources while documenting tests, errors, and reproducible steps.
Overview
This project is an academic IAM lab centered on midPoint. The objective was to understand how identity data can be imported, mapped, propagated, and validated across different resource types instead of staying at a purely conceptual level.
What I worked on
- Connector configuration around CSV, LDAP, and SQL-style resources
- Schema handling and mapping logic inside midPoint
- Provisioning-oriented reasoning: how identity data moves, what breaks, and how to validate the result
- Step-by-step documentation with commands, interface actions, and observed behavior
Why it matters in my portfolio
IAM work is often abstract when presented badly. This project matters because it shows that I can:
- read dense technical documentation
- configure and test connectors methodically
- explain what was done and why
- document both the working path and the troubleshooting path
Technical angle
The most useful part of this lab was understanding that IAM is not only about creating users. It is about:
- data flow
- mappings
- propagation
- resource behavior
- validation and evidence
That makes the project valuable for both systems-oriented and identity-oriented roles.
Current proof included on the page
- an architecture image that makes the connector paths visible instead of implicit
- a validation board focused on connector scope, provisioning, and documentation output
- a block explaining what I personally handled in the lab
- result cards that turn the project into a clearer case study around propagation and testing
What this project demonstrates
- structured work on a complex technical platform
- comfort with Dockerized lab environments
- methodical troubleshooting around configuration and provisioning
- strong documentation habits for technical handover
What can still be added later
This page can later include selected connector configuration extracts, mapping examples, and clean screenshots from the midPoint interface.
Validation board
