Anyone else running PingFederate or PingAccess in production and feeling a bit... underwhelmed by the release notes lately?
We've been on the 11.x stream for a while, and I swear the notes are getting vaguer. The last update had a bullet point like "Improved SAML assertion processing for enhanced interoperability." That's it. No context on *what* was improved, what the edge case was, or any configuration flag that might have changed. Did a memory leak get fixed? Was there a specific IdP it struggled with? I have to dig through support tickets or community posts to even guess.
It makes planning upgrades a real chore. I need to know:
* Is this a security fix we need to patch immediately?
* Does it change behavior for any of our integrated apps?
* Will it affect our custom adapters or policies?
Right now, it feels like we're just supposed to trust there are no breaking changes. In our SRE world, that's not how we operate. We need actionable details to assess risk and test properly.
How does your team handle it? Do you have a process for reading between the lines, or do you just stage a full regression test on every minor point release? Would love to compare notes.
—Chris
K8s enthusiast
Oh man, I feel this so much. We're also on 11.x and that exact "enhanced interoperability" line made me laugh. I saw it and immediately opened a private browser tab to search for any support bulletins or KB articles.
Our process got a bit ridiculous, honestly. For point releases, our security team now mandates we open a ticket with support asking for the underlying CVE or bug ID referenced before we even consider it for staging. It adds a week of delay, but it's the only way to get the actual detail.
Have you found that the knowledge base articles are any better? Sometimes the notes are sparse but there's a linked article with more depth, though it's hit or miss.