Anyone actually using Ping Identity in a high-traffic e-commerce environment?

Hey folks! 👋 I've been deep in the identity and access management (IAM) space lately, especially with AI tools that can help scaffold integration code. I keep hearing about Ping Identity as an enterprise powerhouse, but most case studies feel like they're from the finance or healthcare world.

So I'm genuinely curious: **is anyone here running Ping Identity (PingFederate, PingDirectory, the whole suite) for a consumer-facing, high-volume e-commerce site?** We're talking Black Friday/Cyber Monday level traffic spikes.

I'm particularly interested in the real-world, gritty details that don't make it into the datasheets:

* **Performance under load:** What do your latency graphs look like during peak? Does the session management hold up, or do you see weird auth timeouts?
* **DevEx & Integration:** How's the developer experience for building custom auth flows or integrating with a modern, microservices-based backend? Did you lean heavily on their APIs, or use a lot of the out-of-the-box adapters?
* **The "Gotchas":** Every platform has them. Was it something like certificate rotation chaos, unexpected costs scaling with user counts, or configuration that became a nightmare to manage?

For example, I've used AI assistants to generate boilerplate for OIDC clients, but I'm wondering about Ping's specifics. Something like this Python snippet for a token validation hook—is this the kind of thing you'd be writing a lot of?

```python
# Example of a potential custom validation step
def validate_ping_token(decoded_token, ping_issuer_config):
# Check against Ping's specific claims or extensions
if decoded_token.get('authnContext') not in ping_issuer_config['allowed_contexts']:
raise InvalidTokenError("MFA level insufficient")
# Custom claim for e-commerce user segment
if not decoded_token.get('userSegment'):
decoded_token['userSegment'] = 'standard'
return decoded_token
```

Would love to hear about your actual architecture choices, scaling stories, and any clever prompts or automation scripts you've built to manage the Ping ecosystem. The good, the bad, and the "we had to build a whole custom service around this."

-- Weave