You thought a ldapdelete would be enough. It wasn’t. The data was still there, shadowed in replication, cached in directories, locked in authorization tables. If you can’t guarantee real deletion, you can’t guarantee compliance.
Data access and deletion in LDAP is not just about running commands. It’s about full lifecycle control: identifying where the record exists, who can see it, and how quickly it’s purged across every node. This means querying with precision, verifying permissions on read operations, tracing replication paths, and ensuring that all dependencies are resolved before removal.
Start with accurate discovery. Use filtered LDAP queries to audit current access. Map scopes and attributes to actual consumers—applications, services, scripts. Track which user accounts, service accounts, and group policies have binding permissions. Without this clarity, deletion requests are incomplete and risky.
Then, address deletion as a process, not an event. A single delete operation may not purge shadow entries in persistent stores. Make sure you handle: