To give some context, I work across the Identity Security Vendor space as a Go-To-Market headhunter. Don't worry I'M NOT TRYING TO SELL any services in here!
As a naturally inquisitive person, over the years of working with the vendors in the space, I've become more and more interested in the underlying technology in Identity.
I wholeheartedly believe Identity is at the forefront of the next 10+ years and the more I learn the more I slightly become scared for where we are going.
Open to any questions around whatever topics, going to be posting in here more around what I'm seeing and hearing, as well as my opinions
Managed Service Providers are handling more identities than ever before. Between multiple clients, hybrid environments, remote users, and cloud applications, identity and access management (IAM) has become one of the most complex parts of MSP operations.
Some IAM challenges MSPs commonly face:
Managing identities across multiple client environments
Inconsistent access policies between on-prem and cloud systems
Over-privileged user accounts that increase security risk
Manual onboarding and offboarding are consuming too much time
Limited visibility into who has access to what across clients
Traditional IAM approaches that were effective in the past often struggle to scale in MSP-driven environments. This forces MSPs to rethink how they manage authentication, authorisation, and access control while maintaining security and operational efficiency.
I recently explored why MSPs need a more centralised and scalable IAM strategy, especially to reduce identity sprawl, enforce consistent policies, and improve access visibility across client environments.
I see a lot of discussions around Zero Trust, MFA, and access control, but one problem that keeps showing up everywhere is identity sprawl.
In many environments, users end up with multiple identities across:
Windows endpoints
SaaS applications
VPNs and internal tools
Privileged and non-privileged systems
This often leads to real issues like:
Over-provisioned access
Inconsistent authentication policies
Delayed deprovisioning during offboarding
Limited visibility into who has access to what
This pushed me to revisit the fundamentals of Identity and Access Management (IAM) and how modern IAM platforms are addressing these gaps through centralized identity control, policy-based access, and unified authentication.
A couple of people in here directed me to MidPoint for IGA learning. I cannot thank you all enough by the way. While it’s still a bit locked down, it’s definitely more open than other IGA solutions out there. Yes, I’m looking at you SailPoint and Saviynt. So, if you are eager to learn IGA fundamentals and even get some hands-on experience with IGA workflows, I recommend MidPoint. I’m hoping that adding this to my resume will help me land some interviews, along with my Okta certifications and Entra ID and AD experience.
Which reminds me, should I create a Github account and actually show my MidPoint project or are managers going to be more interested in my knowledge?
I’m Riyad from Hydden, and we’re excited to be at Identiverse this week – Booth 912.
If you’re working on improving your IAM, IGA, or overall identity visibility and hygiene, we’d love to meet you. We focus on helping teams clean up identity data, tighten access controls, and get ahead of audit & compliance risks.
Whether you’re attending to explore new tools, sharpen your program, or just want to chat about identity architecture – swing by and say hi! We’re a small, fast-moving team and always eager to learn from others in the space.
I've read the news that Microsoft has announced the retirement of sms and voice authentication starting February 2027.
AI voice and face clones can be created in minutes, and honestly, that scares me. I'd rather see identity recovery move to on-device verification, where the user's identity can be securely verified using their own device, instead of relying on helpdesk employees to recognize someone's face or voice on a Teams call.
Hello all, I am not sure why there is no reddit community for midPoint, maybe we should create one. :-) I am now closely done with implementing AD.
My opinion to midPoint;
midPoint seems really easy to use compared to products I had in the past. But sometimes it takes longer to get things running, because I have the feeling that the docs are for people who are deeper in the system and error messages are not explained. Googling things is not helpful because there is not as much public community content. But with a bit pain and trial and error I get things running.
Problem;
I think I have imported all XML files to do Active Directory (AD-LDAP Advanced).
I have CSV file located on my linux server with HR data. I have created mappings, generating employeeIDs/unique IDs for AD because our HR systems GUIDs are too long and so on. Creating AD users is working, they show up in local AD and assigning AD groups to roles + writing the memberships back to AD is working. Also AzureAD/EntraID is connected but not tested like the AD resource.
I get sometimes error messages when I am assigning directly AD users to persons and saving the person.
For me it looks like the when there is a assigned AD account, midPoint trys to convert the person to something other. I don't know why this happens. But maybe I am wrong.
I have also created an role for users with AD resource in it and assigning users to this role is not showing this error. Maybe there is an error in the logs which is not popping up in the GUI.
Operation
Save (GUI)
Message
Trying to enforce archetype:00000000-0000-0001-0702-000000000100(Active directory user account) on user:91f5ff4e-f882-4529-a68e-a62e99762448(null) (because of account(ID {.../resource/instance-3}objectGUID = [ ff16299e-daa5-41c1-807a-526d4c688504 ], ACCOUNT/user, resource:75c197a9-1071-4ac8-b8c0-414b1c8eb4f5(AD))); but the object has already a different structural archetype: archetype:00000000-0000-0000-0000-000000000702(Person)
Error
Trying to enforce archetype:00000000-0000-0001-0702-000000000100(Active directory user account) on user:91f5ff4e-f882-4529-a68e-a62e99762448(null) (because of account(ID {.../resource/instance-3}objectGUID = [ ff16299e-daa5-41c1-807a-526d4c688504 ], ACCOUNT/user, resource:75c197a9-1071-4ac8-b8c0-414b1c8eb4f5(AD))); but the object has already a different structural archetype: archetype:00000000-0000-0000-0000-000000000702(Person)[ SHOW ERROR STACK ]
com.evolveum.midpoint.util.exception.PolicyViolationException: Trying to enforce archetype:00000000-0000-0001-0702-000000000100(Active directory user account) on user:91f5ff4e-f882-4529-a68e-a62e99762448(null) (because of account(ID {.../resource/instance-3}objectGUID = [ ff16299e-daa5-41c1-807a-526d4c688504 ], ACCOUNT/user, resource:75c197a9-1071-4ac8-b8c0-414b1c8eb4f5(AD))); but the object has already a different structural archetype: archetype:00000000-0000-0000-0000-000000000702(Person) at com.evolveum.midpoint.model.impl.lens.projector.loader.ContextLoader.checkForArchetypeEnforcementConflicts(ContextLoader.java:258) at com.evolveum.midpoint.model.impl.lens.projector.loader.ContextLoader.enforceArchetypeFromProjection(ContextLoader.java:234) at com.evolveum.midpoint.model.impl.lens.projector.loader.ContextLoader.enforceArchetypesFromProjections(ContextLoader.java:207) at com.evolveum.midpoint.model.impl.lens.projector.loader.ContextLoader.updateArchetypesAndArchetypePolicy(ContextLoader.java:180) at com.evolveum.midpoint.model.impl.lens.projector.loader.ContextLoader.updateArchetypePolicyAndRelatives(ContextLoader.java:158) at com.evolveum.midpoint.model.impl.lens.projector.focus.InboundProcessor.processInbounds(InboundProcessor.java:66) at com.evolveum.midpoint.model.impl.lens.ClockworkMedic.lambda$partialExecute$1(ClockworkMedic.java:194) at com.evolveum.midpoint.model.impl.lens.ClockworkMedic.partialExecute(ClockworkMedic.java:357) at com.evolveum.midpoint.model.impl.lens.ClockworkMedic.partialExecute(ClockworkMedic.java:192) at com.evolveum.midpoint.model.impl.lens.projector.focus.AssignmentHolderProcessor.processFocus(AssignmentHolderProcessor.java:105) at com.evolveum.midpoint.model.impl.lens.ClockworkMedic.lambda$partialExecute$1(ClockworkMedic.java:194) at com.evolveum.midpoint.model.impl.lens.ClockworkMedic.partialExecute(ClockworkMedic.java:357) at com.evolveum.midpoint.model.impl.lens.ClockworkMedic.partialExecute(ClockworkMedic.java:192) at com.evolveum.midpoint.model.impl.lens.projector.Projector.projectInternal(Projector.java:194) at com.evolveum.midpoint.model.impl.lens.projector.Projector.project(Projector.java:88) at com.evolveum.midpoint.model.impl.lens.ClockworkClick.projectIfNeeded(ClockworkClick.java:178) at com.evolveum.midpoint.model.impl.lens.ClockworkClick.click(ClockworkClick.java:106) at com.evolveum.midpoint.model.impl.lens.Clockwork.click(Clockwork.java:417) at com.evolveum.midpoint.model.impl.lens.Clockwork.runWithConflictDetection(Clockwork.java:157) at com.evolveum.midpoint.model.impl.lens.Clockwork.run(Clockwork.java:109) at com.evolveum.midpoint.model.impl.controller.ModelController.executeChangesNonRaw(ModelController.java:355) at com.evolveum.midpoint.model.impl.controller.ModelController.executeChanges(ModelController.java:311) at com.evolveum.midpoint.gui.impl.page.admin.ProgressAwareChangesExecutorImpl$1.callWithContextPrepared(ProgressAwareChangesExecutorImpl.java:145) at com.evolveum.midpoint.gui.impl.page.admin.ProgressAwareChangesExecutorImpl$1.callWithContextPrepared(ProgressAwareChangesExecutorImpl.java:130) at com.evolveum.midpoint.web.component.SecurityContextAwareCallable.call(SecurityContextAwareCallable.java:50) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583)
hey all. I work at Cerbos (we do authorization). This is a pattern I keep seeing in IAM and dev teams:
A lot of folks can see the authorization gap clearly. Policy scattered across app code, no central view of who can do what, agents getting broad access nobody's tracking. But they can't get it prioritized, because it keeps getting framed as an engineering refactor, and refactors lose budget fights.
What actually moves it is reframing the exact same problem in the terms your CISO and board answer to. not "our authorization logic is fragmented," but "we can't prove to a regulator who accessed what, here's our exposure under NIS2, DORA and the EU AI Act, and the CISO is personally on the hook for it." Same gap, completely different urgency once it's a risk and compliance problem instead of tech debt.. (:
We ended up building a CISO facing ebook around exactly that framing, an authorization maturity model with a regulator-by-regulator exposure view and a 90-day plan, specifically so identity teams and software / engineering have something to hand up the chain. it's written in board language, not engineering language, which is the whole point of it. Here if it's useful: https://solutions.cerbos.dev/authorization-maturity-model-a-cisos-benchmark
mostly curious how others here handle this though.. I love getting into these conversations, everyone's situation seems to be a bit different... When you've actually gotten authorization funded, what was the argument that landed with leadership? a specific regulation, an audit finding, an incident, something else?
Hi I dont even know if this is the right sub for this. I have a friend who just got of jail, and his ex gf won't give his brith certificate(he was born aboard), I'd, army papers. I dont know if she lost them or what. But he needs that stuff so he can go to the homeless shelter. What can he do?
I’m running a live Identity & Access Management (IAM) workshop soon — super beginner-friendly and perfect if you’re looking to break into IAM or prep for the CIAM cert.
As a little thank-you to the Reddit fam, I’ve made a discount code just for you:REDDIT-IAM 🙌
You’ll get:
Live sessions with Q&A
Study guide + practice questions
Free Udemy course access
CIAM Certification prep
CIAM Certification discount code
If you’re curious or got questions, just drop a comment — happy to chat!
Identity and Access Management (IAM) is one of the simplest and most powerful foundations a startup can put in place. It ensures that the right people and the right systems can access your product safely nothing more, nothing less.
Today, this idea goes beyond just users. With the rise of Agentic AI, AI systems that act on their own, make decisions, and perform tasks startups now need to protect not only human access but AI agent access as well. This is where IAM and MCP-based security come together.
I am currently working in Microsoft as support engineer for entra id whole with 1.2 years of experience How many years of experience is required for me to get a job outside as iam expert or related roles considering i am far more familiar with the product as a whole My current ctc is 10.2lpa