Symptoms: The front-end or back-end API used to retrieve the current user session returns null.įix: Session info is no longer cached and when the user session has expired the vSphere Client automatically displays a modal dialog indicating the user needs to login again.
Plugin requests fail with missing user session. Integration with user settings for theming and date formatting.Plugin view navigation with custom data.Linking a Summary section with a Monitor or Configure view for more details.More standard UX patterns following the UX Design Guidelines for vSphere Client Plugins.New versions of the referenced libraries: Clarity Design System 1.1 and Angular 7.When the URL parameter pluginDeveloperMode=true is set the Client Plugins view contains a REDEPLOY button which triggers plugin re-installation. Ability to redeploy local and remote plugins in dev mode.Increased maximum height of a modal dialogs for modals which require more space.
Using SHA-1 thumbprints is still supported. Support for SHA-256 thumbprints for plugin extensions with the vCenter Server.This is a relative location enabling the plugin to properly reference its resources. Allow remote plugin views to retrieve their proxied plugin server origin (see new app.getProxiedPluginServerOrigin API).Ability to navigate from one remote plugin to another (see new app.navigateToRemotePluginView and app.getRemotePluginNavigationMap APIs).Local and Remote plugins can open a lightweight confirmation modal (see new modal.openConfirmationModal API).Local and Remote plugins can f format plugin dates and subscribe for date and time format changes (see new app.formatDateTime and app.onDateTimeFormatChanged APIs).More information about this feature can be found in the Using Themes with vSphere Client Plug-ins chapter of the official SDK documentation. Theme-specific icons for both local and remote plugins.Remote plugin support for multiple plugin server registrations with a single vCenter Server (see new app.getPluginBackendInfo() API).The shortcut is generated by the vSphere Client based on the known plugin display name and icon. Remote plugin shortcuts are displayed in a dedicated Plugins section on the Shortcuts page.Integration within the vSphere Client categories is no longer available. All Monitor and Configure extensions are now placed under a dedicated plug-in category or moved directly at the root of the Monitor/Configure table of contents.Plugins rely on the iframe URL but not on the URL format of vSphere Client pages which is not a public API.This change is transparent to all API navigation calls initiated by the plug-in, all URLs specified in the plugin manifest and old user bookmarks using extension ids.No changes to existing plugins are required.They are no longer based on extension IDs. The URLs of vSphere Client pages are now using a router syntax made of multiple paths.RBAC support through a new vCenter Server privilege: Plugin.Management.Enhancements to enabling and disabling plugins:.Automatic detection and undeployment of plugins unregistered from the vCenter Server Extension Manager (no vSphere Client restart required).Automatic detection and deployment of plugins registered or updated with the vCenter Server Extension Manager (no new user login required).This release of the vSphere Client and the SDK introduces the following features and improvements: vSphere Client plugin management improvements The vSphere Client 7.0 SDK enables development of vSphere Client plugins supported on both vSphere and VMware Cloud on AWS. The release notes cover the following topics: VSphere Client SDK 7.0 | 02 APRIL 2020 | Build 15863815Ĭheck for additions and updates to these release notes.
0 kommentar(er)
