Quantcast
Channel: VMware Communities : Discussion List - vSphere Client SDK
Viewing all articles
Browse latest Browse all 2218

Error with local deployment of a vcenter plugin using vSphere Client SDK 6.7.0

$
0
0

Hi all,

I want to develop my custom vCenter plugin, so I deploy vSphere Client SDK in my development machine, but in the end, I failed to access https://localhost:9443/ui, it shows that "[400] An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - null."

截图.PNG

Help highly appreciated

 

What I do:

  1. my development machine is Windows 10, its environment is:

         --java: 1.8.0_60

         --ant: 1.9.15

    2. I have a VCSA6.7(VMware vCenter Server Appliance 6.7.0), and I can access it normally

       

     3. Download vSphere Client SDK 6.7.0 from https://code.vmware.com/web/sdk/6.7/client

     4. Extract the content of the SDK in a directory, then set the VSPHERE_SDK_HOME and VMWARE_CFG_DIR environment variables:

         

   5. Register My Local vSphere Client with the vCenter Server Instance

       -- Run the dev-setup.sh on my VCSA

               root@vcsa158 [ ~ ]# sh dev-setup.sh

               Generating store.jks file...

               Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

               Importing keystore store.p12 to store.jks...

               Entry for alias vsphere-webclient successfully imported.

               Import command completed:  1 entries successfully imported, 0 entries failed or cancelled

               Warning:

               The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore store.jks                -                      destkeystore store.jks -deststoretype pkcs12".

               Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

               Certificate was added to keystore

               Warning:

               The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore store.jks                     destkeystore store.jks -deststoretype pkcs12".

               Generating webclient.properties file...

               Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

               Creating ds.properties file...

               Done.

       --Copy the three generated files on my dev machine

          webclient.properties  --    C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client

          ds.properties  --    C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\config

          store.jks    --    C:\ProgramData\VMware\vCenterServer\cfg

   6. Run the startup script to start the local vSphere Client

7. Failed to access https://localhost:9443/ui


Viewing all articles
Browse latest Browse all 2218

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>