I had the same issue, and done the same procedure over and over with the support. And we haven't found a solution so far. But in my case, I only get this error in my prod, where I have 2 VRO Server. And I will get this error only on the second node. In my preprod, I also have two vro Server, both linked to another Active Directory, and both vro nodes are working without issue.
Also, when doing the reset it will not reset the sso authentification done within the VRO Server, but it will reset the authentication with the Control Center.
But also, this issue helped me realized that with a cluster and sso, 7.3 is not yet ready. I mean the cluster part is working fine, but I don't have enough control over the cluster. When the cluster is enabled, and sso is activated for the Control Center, you loose access to connect to node 1 or node 2 specifically. So, you cannot restart a specific node, by reading the documentation regarding the cluster information and load balancing stuff, something is not right.
Because if you have vro node 1 down, and want to restart it. You access the control center which is now load balanced, but the monitor is based on the documentation page, which will probably work since its monitoring the control center service, but what you need to restart is the vro server, so you can't access node 1 via http directly because you could be redirected to whatever node the load balancer decides. Anyway I reported that to the dev team already.
Also, the access to http is vital to me, since our security team prevent us from using ssh. ssh should be enabled in extreme cases. So for this reason, I've removed the sso authentication from the Control Center, and now I'm only using root.
Another detail, when doing the reset, and reconfiguration, you will need the account/password to authenticate with your vcenter/psc, important to know since in my case I don't have that account, I must always get the team that does...
