openiam.com ↗ · required email domain for this vendor's users
Has anyone other than the vendor confirmed this?
Nothing here has been confirmed by an independent third party yet.
Is this a real, durable business?
How long this vendor has been operating, and who stands behind them.
What do they do when something goes wrong?
What their public record shows about handling vulnerabilities and outages.
Do they tell you the awkward things unprompted?
We have not checked what this vendor discloses publicly yet.
Nothing checked here yet — this is not a mark against OpenIAM.
Are they still shipping, or coasting?
We have not tracked this vendor's release activity yet.
Nothing checked here yet — this is not a mark against OpenIAM.
Not a quality rating or endorsement — a measure of how much verified, disclosed data we actually have about this vendor. A low score usually means "we don't have much verified information yet," not "this is a bad vendor." Never used to sort or rank vendor lists.
The platform admin controls the formula's weights.
No buyer reviews yet.
No ratings in this window yet.
Customer IAM platform for managing external identities with SSO and MFA AI-generated from public sourcesAuto-generated by 0-Doubt from public vendor materials. Not verified by the vendor or an analyst. Check the freshness indicator.Lowest independence — unverified. A higher label means a more independent source — not a better product.How trust works →
OpenIAM before 4.2.0.3 does not verify if a user has permissions to perform /webconsole/rest/api/* administrative actions.
OpenIAM before 4.2.0.3 has Incorrect Access Control for the Create User, Modify User Permissions, and Password Reset actions.
OpenIAM before 4.2.0.3 allows remote attackers to execute arbitrary code via Groovy Script.
OpenIAM before 4.2.0.3 allows Directory Traversal in the Batch task.
OpenIAM before 4.2.0.3 allows XSS in the Add New User feature.