WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / Home Lab / vYetti - Fun animated vSphere Login UI customization

vYetti - Fun animated vSphere Login UI customization

05.15.2018 by William Lam // 10 Comments

For those that have been asking about how to customize the vSphere Client Login UI to include this fun little animated login screen as shown below, you can find the complete instructions on my github repo: https://github.com/lamw/vyetti-vsphere-client-customization

I wanted to take a moment and give thanks and credit to the original author (Darin S) who created the animated login, which he referred to as an "Animated SVG Avatar". I remember seeing this on my Twitter stream a few months back where it was shared on codepen.io, which is a platform for web developers to easily show off their demos. From what I could gather, the original demo had used MorphSVGPlugin.min.js which is a Javascript library that provided the animation. Apparently, the use of this library required a membership which prevented anyone from consuming this outside of codepen.io for demo purposes. While searching online, I accidentally stumbled across another similiar project by Balram Chavan who developed an alternative solution simply using Angular 5. With Balram's solution, I was able to make the necessary minor modifications (thanks to Jeeyun from the Clairty team on helping me with some of my Anuglar questions) to get this fully incorporated into the vSphere Client UI. I am sure there are other improvements that can be made to the customization such as a more "clarity" look/feel as the old the old "blue marge" theme background is pretty dated but I will leave that to someone more creative than me 🙂

More from my site

  • Changing "Password will expire in X days" notification for Active Directory users in vSphere Web/H5 Client
  • Quick Tip - Pre-filled credentials in the vSphere 6.0 Web Client
  • Quick Tip - Enabling HTML5 VM Console in the vSphere Web Client for IE
  • My top 5 favorite enhancements to the new vSphere Web Client 5.5
  • How to restrict vSphere UI access while maintaining vSphere API functionality?

Categories // Home Lab, Not Supported, vSphere Web Client Tags // HTML5, vsphere web client

Comments

  1. André Pett says

    05/15/2018 at 9:23 am

    No animated CormacH login this time? ;-)))

    Reply
    • William Lam says

      05/15/2018 at 9:41 am

      haha, are you volunteering to create one for him? 😉

      Reply
  2. Tom says

    05/31/2018 at 5:01 am

    Hi William,

    I like this idea very much and I tried to follow your instructions but I'm already struggling with step 1, because I can't find the root.war in the directory you specified.

    I only find it in /usr/lib/vmware-psc-client/webapps/ROOT.war

    I tried to find this in the directory you provided on three different VCSA 6.5 - but without any luck.

    Any ideas?

    Reply
    • Jon Kensy says

      06/03/2018 at 4:05 pm

      Do you have an external PSC? If so, this needs to be performed on the PSC not VCSA

      Reply
    • Anonymous says

      06/21/2018 at 9:35 am

      It's in /usr/lib/vmware-sso/vmware-sts/webapps/websso.war, but requires code modification to work with 6.5 envoirement.

      Reply
  3. Daniel says

    06/03/2018 at 2:00 pm

    Is each WAR file independent? I have a few linked vCenters in my lab...can I just copy the WAR I file generated for vc01 to each vCenter in the domain?

    Reply
  4. Kristen says

    06/10/2019 at 10:50 am

    How do you revert back to the original with ROOT.war.bak?

    Reply
    • William Lam says

      07/02/2020 at 6:12 am

      You just "cp" it back to the original path/filename 🙂

      Reply
  5. Tom says

    07/01/2020 at 5:38 am

    Is this available for vCenter 7.0? Seems like fun, but I'm already running ESXi 7.0 and VCSA 7.0.

    Reply
    • William Lam says

      07/02/2020 at 6:11 am

      Tom,

      With each release of vSphere and specifically the VCSA, the required files that need to get modified can/will change. This means, you need to follow the directions and build the specific .war file for each release you wish to use this with

      Reply

Thanks for the comment! Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • vSphere with Tanzu using Intel Arc GPU 01/26/2023
  • Quick Tip - Automating allowed and not allowed Datastores for use with vSphere Cluster Services (vCLS) 01/25/2023
  • ESXi with Intel Arc 750 / 770 GPU 01/24/2023
  • How to bootstrap vSAN Express Storage Architecture (ESA) on unsupported hardware? 01/19/2023
  • Automating Virtual Machine screenshots in vSphere 01/18/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023