I would encourage you to discuss this further with your Customer Success Manager, as they should be better placed to explain the roadmap and gather feedback.
Hi JackLacava ,
I'm a software developer and, truthfully, I'm a bit out of the loop from the discussions with the Success Manager. My only role was to fix the REST api after it stopped supporting OIDC.
It seemed to me that the OS tech support engineers were also caught off guard by the sudden changes in authentication, and I'd venture to say that a Customer Success Manager wouldn't be any closer to the technical answers that I'm looking for in this case.
Based on the ambiguity in the docs , I'm hoping it was not the intention to break OIDC and hopefully they will bring it back. I'm not sure *why* the product team would want to remove the support for this open authentication standard. And if they did want to do that in an intentional way, it seems like it would have been well-communicated.
I suspect the changes that are being done by this team (OIS) are work-in-progress. One of the purposes of this post is to talk to other technical users, rather than sales teams. And another purpose is to raise awareness so that other customers won't step blindly into v8 without setting aside time to start adopting these OS-specific PAT tokens on native OS user accounts.
Hey,
I suggested CSMs because they can mobilize resources that are not necessarily available to Support, particularly when it comes to discussing the roadmap. Although we're obviously all pushing to do the best for our customers, Support will typically try to get your system running with what we have today, whereas CS can take a more collaborative approach and find ways to make everyone happy in the medium/long term, involving product teams if necessary.
For the record, I've brought this to the attention of the relevant groups, so hopefully your CSM will soon get in touch to discuss the matter in a competent way.
