Issue 93222 - Webdav/https and valid certificate
Summary: Webdav/https and valid certificate
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.4.0
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp, oooqa
Depends on:
Reported: 2008-08-28 17:05 UTC by marinew
Modified: 2014-02-04 17:50 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description marinew 2008-08-28 17:05:06 UTC

I have a Webdav server (Alfresco), accessible through https, signed with a valid

However, when I open a document through Webdav with OOo Writer 2.4 or 2.4.1
(Windows XP), I have the following warning message (in french, sorry) :

    Le certificat n'a pas pu être validé.

    Emis pour : www.<ourWebsite>.fr
    Emis par : TBS X509 CA business
    Valide du 04/11/2008 au 04/13/2009

    Chemin de la certification :
    => AddTrust External CA Root
    ==> TBS X509 CA business
    ===> www.<ourWebsite>.fr

This error appear every day (after complete closing of OOo), which is annoying.

In Thunderbird / Firefox authorities list, I have :
    AddTrust AB
    => AddTrust External CA Root
In Internet Explorer, I have "Autorités intermédiaires" :
    Délivré à : AddTrust External CA Root - Délivré par : UTN-USERFirst-Hardware
    Délivré à : TBS X509 CA business - Délivré par : AddTrust External CA Root

And when I browse our Alfresco website through Firefox or IE, I have no
certificate warning.
It seems that OOo don't care about these autorithies ?

Thanks in advance.
Comment 1 michael.ruess 2008-08-29 06:12:56 UTC
Framework issue.
Comment 2 Mechtilde 2010-05-21 09:21:51 UTC
does it still exists with 3.2.0 or newer?

which OS do you use?
Comment 3 strob 2010-05-21 11:43:30 UTC
I've tried it with DEV320m12 on Windows and Linux. I didn't try it with newer
versions yet.

This pop-up-message maybe is a more general problem associated with opening
different contents via HTTPS-connections (also for those, which are in the
firefox server certificate list).

Fast steps to reproduce on linux:
* open "" with firefox
* make an exception for the certificate
* make firefox to OOo's certificate pool (as described in

* write in the command-line: swriter "" -> works, no pop-up
* write in the command-line: swriter "" -> works not, at
first time a pop-up appears