Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Edit Trust button missing in 31.x versions?

  • 3 wotmołwy
  • 1 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot 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

Wubrane rozrisanje

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.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (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

Wubrane rozrisanje

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.