Thanks for your reply.
1. That's the proper URL to the Javadoc. The problem is that not all libraries part of the SDK have their Javadoc generated/bundled in the appliance. Not sure why.
Ok, I understand.
2. The problem here is that the libraries in vRO repository are split into two bundles - one public and one related to interactions with other VMware products, eg. SSO. In old vRO releases, there were some issues around how to legally package and distribute the second bundle, and that's why you don't see the libraries from this bundle in the hosted Maven repository. Not sure what is the situation with the latest vRO releases (6.x and 7.x); perhaps these legal issues are not applicable anymore.
For the time being, if you can't find some library in the hosted Maven repository (like o11n-rest-client-sso), you can retrieve its jar file from the libraries used by vRO server and Control Center; search under /usr/lib/vco/app-server/ and /usr/lib/vco/configuration/
I found "/usr/lib/vco/configuration/lib/ext/o11n-rest-client-sso.jar" at vRO server.
It contains SsoAuthenticator class. Thanks a lot. :smileylaugh::smileylaugh::smileylaugh:
I have an another question.
Documents of vRO SSO says that SsoAuthenticator class has a constructor which has four arguments.
//create a factory for vCenter Single Sign-On tokens
SsoAuthenticator sso = new SsoAuthenticator(URI ssoUri, URI adminUri, VcoSessionFactory vcoSessionFactory, long lifeTimeSeconds);
Using vCenter Single Sign-On Authentication with the Orchestrator REST API
But "adminUri" is not described at sample code.
What I use for adminUri?
