![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
bga68compvYetti - Animated vSphere Login UI customization
Requirements
Step 1 - Lets first take a backup of the original ROOT.war file so you can easily revert back in case you run into any issues. To do so, login to VCSA via SSH and run the following command:
Step 2 - We are now going to create a temporary directory that we will use to store the ROOT.war file and we will also copy over it over using the following two commands:
Step 3 - We are now going to change into our /root/ROOT directory and extract the contents of the war file so we can make our modifications. To do so, run the following three commands:
Step 4 - If you wish to pre-fill the credentials when logging into the vSphere Client (Flex/H5), go ahead and update WEB-INF/views/unpentry.jsp as outlined in this blog article here. If you wish to make the login button active so you do not have to click into the box or hit tab, you will need to comment out $('#submit').prop('disabled',true); on L91 in resources/js/websso.js
Step 5 - Copy app.component.css to /root/ROOT/resources/css/ directory
Step 6 - Copy login-animation.js to /root/ROOT/resources/js/ directory
Step 7 - Copy unpentry.jsp to /root/ROOT/WEB-INF/views/ directory
Note 1: If you are NOT using VCSA 6.7, you should use the original unpentry.jsp and apply the specific animated login code, as the file is different in older versions of VCSA
Note 2: If your vCenter Server can NOT directly access the internet, you may also need to download the TweenMax.min.js file and store that locally under /resources/js
Step 5 - Next, we need to re-generate the ROOT.war file so we can replace it with our modified version. To do so, run the following command:
If the command was successful, we should have our new ROOT.war located in /root.
Step 6 - Now we just need to update the system with our modified ROOT.war by simply copying it back to the original location by running the following command:
Finally, to verify that that our changes will go into effect, we can simply issue a reboot to our VCSA and we should see that any customization changes made to the vSphere Client Login UI will now persist after a system restart.
Источник:
https://github.com/lamw/vyetti-vsphere-client-customization/blob/master/README.md
Requirements
- vCenter Server Appliance 6.5+ or 6.7
Step 1 - Lets first take a backup of the original ROOT.war file so you can easily revert back in case you run into any issues. To do so, login to VCSA via SSH and run the following command:
cp /usr/lib/vmware-sso/vmware-sts/webapps/ROOT.war /usr/lib/vmware-sso/vmware-sts/webapps/ROOT.war.bakStep 2 - We are now going to create a temporary directory that we will use to store the ROOT.war file and we will also copy over it over using the following two commands:
mkdir /root/ROOT
cp /usr/lib/vmware-sso/vmware-sts/webapps/ROOT.war /root/ROOT/Step 3 - We are now going to change into our /root/ROOT directory and extract the contents of the war file so we can make our modifications. To do so, run the following three commands:
cd /root/ROOT
unzip ROOT.war
rm ROOT.warStep 4 - If you wish to pre-fill the credentials when logging into the vSphere Client (Flex/H5), go ahead and update WEB-INF/views/unpentry.jsp as outlined in this blog article here. If you wish to make the login button active so you do not have to click into the box or hit tab, you will need to comment out $('#submit').prop('disabled',true); on L91 in resources/js/websso.js
Step 5 - Copy app.component.css to /root/ROOT/resources/css/ directory
Step 6 - Copy login-animation.js to /root/ROOT/resources/js/ directory
Step 7 - Copy unpentry.jsp to /root/ROOT/WEB-INF/views/ directory
Note 1: If you are NOT using VCSA 6.7, you should use the original unpentry.jsp and apply the specific animated login code, as the file is different in older versions of VCSA
Note 2: If your vCenter Server can NOT directly access the internet, you may also need to download the TweenMax.min.js file and store that locally under /resources/js
Step 5 - Next, we need to re-generate the ROOT.war file so we can replace it with our modified version. To do so, run the following command:
zip -r /root/ROOT.war index.jsp META-INF resources WEB-INFIf the command was successful, we should have our new ROOT.war located in /root.
Step 6 - Now we just need to update the system with our modified ROOT.war by simply copying it back to the original location by running the following command:
cp /root/ROOT.war /usr/lib/vmware-sso/vmware-sts/webapps/ROOT.warFinally, to verify that that our changes will go into effect, we can simply issue a reboot to our VCSA and we should see that any customization changes made to the vSphere Client Login UI will now persist after a system restart.
Источник:
https://github.com/lamw/vyetti-vsphere-client-customization/blob/master/README.md
