![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
"Friendly Names" not showing for certificates imported into Firefox
I've set "friendly names" for my personal certificates using MMC in windows and those names work fine in IE and Edge.
However, when I import those certificates into Firefox, the friendly names do not appear and there seems to be no way of setting them in Firefox's certificate store. I did export them using MMC with "all extended properties".
How can I get the friendly names to show, or set them in Firefox? Juggling certificates gets frustrating without them.
Thanks!
Todas as respostas (2)
https://www.digicert.com/util/utility-edit-friendly-name.htm see page end as per Note: If you are using a Wildcard certificate with multiple websites, you may want to begin your friendly name with a wildcard character * (e.g. *your.domain-digicert-(expiration.date)). This naming convention makes it easier to identify the wildcard certificate so that you can assign it to multiple websites. No idea where you got your certificates are the made by you or are they issued by a company. If issued by a company then see their web site for help.
Pkshadow said
https://www.digicert.com/util/utility-edit-friendly-name.htm see page end as per Note: If you are using a Wildcard certificate with multiple websites, you may want to begin your friendly name with a wildcard character * (e.g. *your.domain-digicert-(expiration.date)). This naming convention makes it easier to identify the wildcard certificate so that you can assign it to multiple websites. No idea where you got your certificates are the made by you or are they issued by a company. If issued by a company then see their web site for help.
Unfortunately, when I try to import a certificate into the utility in order to edit the Friendly Name, I get the error "The File <name> does not have any SSL or code signing enabled certificate contained in it."
It's a .pfx file, and I'm able to import it just fine into FF and use it in FF, so I think it's intact.