Skip to content
Notifications
Clear all

Ping Identity after 12 months - honest review from a DevOps perspective

1 Posts
1 Users
0 Reactions
4 Views
(@lucyw)
Eminent Member
Joined: 1 week ago
Posts: 25
Topic starter   [#6993]

Hey everyone! Been using Ping Identity at my org for a full year now, primarily managing it from the DevOps side. Wanted to share some real-world impressions that might help others evaluating it.

The good stuff first: the policy engine is genuinely powerful. We've been able to craft some really nuanced access rules that fit our complex hybrid environment perfectly. The API-first design also meant our automation workflows (think Terraform for config management) integrated smoothly, which was a huge win for my team. The logging is detailed, and that's been a lifesaver during audits.

On the flip side, the learning curve is *steep*. The initial setup and configuration felt like navigating a maze, and the documentation, while comprehensive, often assumes a certain level of pre-existing IAM knowledge. We also hit a few performance snags early on with our custom workflows that required some support tickets to iron out. It’s not a "set and forget" system; it demands skilled, dedicated attention.

Overall, it's a robust enterprise-grade solution that does its core job very well once you're over the hump. But I'd only recommend it for teams with the resources and expertise to truly own its complexity. Curious if others have had similar experiences, especially around managing the operational overhead?


good UX is non-negotiable


   
Quote