Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Edit Trust button missing in 31.x versions?

  • 3 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 3 gösterim
  • Son yanıtı yazan: kvaden

more options

We need to Trust an LDAP cert for our Address Book lookup to function. In the past (pre 31.x versions) we would Import the cert for the LDAP server, then use the "Edit Trust" button (see attached image from 24.4.0 version) on the Servers tab to Trust it. That "Edit Trust" is no longer present in newer versions. Since our ESR versions stay updated for security-compliance reasons, the Address Book is now broken for many of our users. How do we get it back, or perform the same Trust function with the latest versions?

TIA, KV

We need to Trust an LDAP cert for our Address Book lookup to function. In the past (pre 31.x versions) we would Import the cert for the LDAP server, then use the "Edit Trust" button (see attached image from 24.4.0 version) on the Servers tab to Trust it. That "Edit Trust" is no longer present in newer versions. Since our ESR versions stay updated for security-compliance reasons, the Address Book is now broken for many of our users. How do we get it back, or perform the same Trust function with the latest versions? TIA, KV

Seçilen çözüm

Thanks, but Diginotar was just a random example cert I clicked on to illustrate the dialog.

As for the solution, I figured it out…you have to add a Server exception using the correct syntax to get a response from the server, in this case: https://our-sites-ldap-server.com:636

Problem solved.

Bu yanıtı konu içinde okuyun 👍 0

Tüm Yanıtlar (3)

more options

Image referenced in original post attached, wouldn't work on initial post.

Tx, KV

more options

If you still use a cert issued by Diginotar you're doing something wrong. https://blog.mozilla.org/security/2011/09/02/diginotar-removal-follow-up/

more options

Seçilen çözüm

Thanks, but Diginotar was just a random example cert I clicked on to illustrate the dialog.

As for the solution, I figured it out…you have to add a Server exception using the correct syntax to get a response from the server, in this case: https://our-sites-ldap-server.com:636

Problem solved.