After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 652814 - Move certificate configuration to advanced preferences
Move certificate configuration to advanced preferences
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: Accounts
unspecified
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on: 652811 652830
Blocks:
 
 
Reported: 2011-06-17 11:28 UTC by Stef Walter
Modified: 2018-05-22 14:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stef Walter 2011-06-17 11:28:21 UTC 
Move override/configuration of certificate to advanced preferences.

The concept for this is 'Pin a certificate to this Account'.

Done during configuration, rather than later randomly while connecting. Connection will fail for an invalid or untrusted certificate, and then you can go into configuration and setup the certificate.

In the configuration dialog "Advanced" section, there's a button:

    [Pin certificate to this Account]

Clicking opens dialog:

     Retrieving Certificate...

     [Add Pinned Certificate] [Cancel]

Once loaded:

     Certificate Information XXXX
                             XXXX
     v Details               XXXX

     [Add Pinned Certificate] [Cancel]

After added closes, and the certificate shows in the advanced section, instead of the pin certificate button. Can then click that button to get similar UI to examine the certificate and remove the pinning.
Comment 1 Stef Walter 2011-06-17 13:39:33 UTC 
Related telepathy work: https://bugs.freedesktop.org/show_bug.cgi?id=38404
Comment 2 GNOME Infrastructure Team 2018-05-22 14:50:30 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/empathy/issues/389.