This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

SEC_ERROR_UNKNOWN_ISSUER with internal CA on Ubuntu 16.04 Thin-Clients

  • 1 antwoord
  • 0 hierdie probleem
  • 2 views
  • Laaste antwoord deur Tekkion

Tekkion
Tekkion
more options

Hi,

im getting unknown issuer on my thin-clients with a FF ESR 45.9.0. This FF is tied to the OS (Ubuntu 16.04) and the OS is the most recent compatible version for our version of the thin-clients. So yeah its super old and I'm not able to update any of this. There is no security.enterprise_roots.enabled option available. What would be the best way to solve this issue for ~400 clients. Thanks in Advance Regards Tekkion

Hi, im getting unknown issuer on my thin-clients with a FF ESR 45.9.0. This FF is tied to the OS (Ubuntu 16.04) and the OS is the most recent compatible version for our version of the thin-clients. So yeah its super old and I'm not able to update any of this. There is no security.enterprise_roots.enabled option available. What would be the best way to solve this issue for ~400 clients. Thanks in Advance Regards Tekkion

Gewysig op deur Tekkion

Gekose oplossing

Ok I was able to deploy the CA certificate via our thin-client management. Beforehand I just made an error not specifying the correct type of certificate. Now its working as expected.

Lees dié antwoord in konteks 👍 0

All Replies (1)

Tekkion
Tekkion Vraag-eienaar
more options

Gekose oplossing

Ok I was able to deploy the CA certificate via our thin-client management. Beforehand I just made an error not specifying the correct type of certificate. Now its working as expected.