Hi,
Finally SSO is load balanced!!..
I came to update the post and read your reply.
Error 20010: fuj it man, I did approx 9-10 re-installation coz of that.. and then I figured out better to install both nodes without updating SSL on node1.
Even updating the ssolscli.jar file did not work.
I updated ssolscli.jar on both nodes after installing SSO.
the server.xml file I think was the key to make it happen.. I was doing a silly mistake.. didn't put the jvmRoute="SrvName" i.e., jvmRoute="SSOA"
did this changes on both nodes, Node1 have SSOA and Node2 have SSOB.
after installtion of SSO, updated root-trust.jks on both nodes.
and updated the endpoints to https://ssoa.domain.com:7444/lookupservice/sdk
I also prepared a complete step-by-step and will upload the article once I do the testing throughly..
But for now, I am able to login to vCenter web client even if Node1 is offline / disconnected..
I can see on LB that traffic for sso-adminserver is not going through.. and yes thats coz the service is available on Primary node only.
And in my lab, i dont need to restart service to make it work after primary node has dropped out.
I will restart the vCenter server while Node1 is offline and will check what happens..
If what engrr said, then there is no point in putting this all together..