> The reason for all these certificate authorities seems to be: the applications need to enable TLS on their local web server. Yet no real certificate authority

> The reason for all these certificate authorities seems to be: the applications need to enable TLS on their local web server. Yet no real certificate authority will issue a certificate for 127.0.0.1, so they have to add their own. Modern browsers will treat http://127.0.0.1/ http://127.0.0.1/ as a secure origin (i.e. you can load resources from it from within a secure website without triggering mixed content warnings) specifically to make hacks like this unnecessary. (Depending on the exact browser and version, you may need to use either the IP or "localhost" - one of them isn't universally supported in older versions). There would be other workarounds, but the correct solution is this, if this kind of portal is in fact required/a good idea in the first place.