I've tried to use the code as in : https://vdc-download.vmware.com/vmwb-repository/dcr-public/1cad846e-1b2f-406f-ba81-34bd77d9bad9/dfb037cd-ff63-4d5e-b432-9a4aa790168f/doc/GUID-ED253BD0-E9B1-4588-95...
See more...
I've tried to use the code as in : https://vdc-download.vmware.com/vmwb-repository/dcr-public/1cad846e-1b2f-406f-ba81-34bd77d9bad9/dfb037cd-ff63-4d5e-b432-9a4aa790168f/doc/GUID-ED253BD0-E9B1-4588-958D-577A667F5AD9.html But client.createStub() , si.RetrieveContent() methods are not detected on the respective classes like for example: "The method RetrieveContent() is undefined for the type ServiceInstance".
After obtaining the "session_clone_ticket", I'm trying to clone the ticket using sessionmanager.cloneticket() but it fails throwing "Unauthenticated" error. What am I doing wrong?
Thank you for clearing that up. We need to have our remote plugin supported for all the most used versions of vcenter. I believe that many customers still use 6.7 U3. Our remote plugin would contain ...
See more...
Thank you for clearing that up. We need to have our remote plugin supported for all the most used versions of vcenter. I believe that many customers still use 6.7 U3. Our remote plugin would contain lot more new features which are not available in old plugin. Since moving forward, vmware recommends the usage of remote plugin itself, we are focusing all our dev on remote plugin itself and not on the old local plugin. As a workaround, we can still right click on link and use "Open in New tab" option and still get it opened in another tab though. We still have to discuss and make a call on that.
We are trying to move to a remote plugin instead of a local plugin that vcenter supports right now. We do have some help links that user can click on which will open help page in a new tab in browser...
See more...
We are trying to move to a remote plugin instead of a local plugin that vcenter supports right now. We do have some help links that user can click on which will open help page in a new tab in browser. This mechanism works for local plugins even for 6.5 vcenter. But for a remote plugin, I'm seeing this issue. Does it mean that popups are allowed for local plugins ? How does it work for local plugins? Can we replicate the same mechanism for remote plugin?
For our client plugin(remote plugin) in vcenter, the iframe sandbox attributes has "allow popups" in vcenter 7.0 U2 whereas the sandbox doesn't have "allow popups" attribute in vcenter 6.7 U3. Could...
See more...
For our client plugin(remote plugin) in vcenter, the iframe sandbox attributes has "allow popups" in vcenter 7.0 U2 whereas the sandbox doesn't have "allow popups" attribute in vcenter 6.7 U3. Could you confirm if it is allowed in vcenter 6.7 ? If not, is there a way to enable the same? Any suggestions would be helpful. Thanks in advance. This is the error that we see for vcenter 6.7 when we try to open a page that is supposed to open in a new tab: "Blocked opening '//<>/index.html' in a new window because the request was made in a sandboxed frame whose 'allow-popups' permission is not set."
