Sorry, I take a while before reply...
Shortly...
Now it works. I connected to vCenter using console and stopped vCenter service using "service vmware-vpxd stop".
After that it was possible to deploy SSO even if the procedure is a little bit obscure as you cold change absolutely nothing, all parameters are disables. So it was deployed and working but at first moment I thought it's not...
Finally I had a embedded SSO, so I gave vcenter address as SSO with default port and it worked.
Good, we have VDP now! :-)))))))))))))))))
About your question...
>I did not think VCVA would actually start without SSO. I thought SSO was installed by default.
Sure it would.
I don't know is it possible to install new VCVA without SSO, but at migration process from 5.0 to 5.1 it was possible to choose "not use SSO".
And IMHO it's good for my point of view. Sure SSO have some utility, but I think for the most of use-case it's just unnecessary.
>I see that there is an option to point SSO to an external SSO server - the catch
> being that the server has to be an appliance! (http://pubs.vmware.com
>/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-A26A99E5-EC3D-48FB-A5D2
>-A9836D6C4E37.html)
Certainly, but if you do not want to have a SSO at all you all the more so not want to have an external SSO.
At least an embedded if it's not possible to live without SSO but certainly not an external.
Fortunately it was worked with silent "do nothing" embedded SSO. :-)
Anyway, thanks for your reply.