We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

SEC_ERROR_UNKNOWN_ISSUER with internal CA on Ubuntu 16.04 Thin-Clients

  • 1 risposta
  • 0 hanno questo problema
  • 2 visualizzazioni
  • Ultima risposta di 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

Modificato da Tekkion il

Soluzione scelta

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.

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (1)

Tekkion
Tekkion Utente che ha posto la domanda
more options

Soluzione scelta

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.