View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003535 | SOGo Connector | with external server | public | 2016-02-17 20:54 | 2016-07-22 19:39 |
| Reporter | timdrub | Assigned To | ludovic | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | Linux | OS | Mint | OS Version | 17.3 |
| Product Version | 31.0.1 | ||||
| Summary | 0003535: SOGo Connector corrupts KEY field and uploads back to server | ||||
| Description | I use Outlook CalDAV Snychronizer to sync contacts from Office365 to a SabreDAV server. I then use Thunderbird w/SOGo Connector to make the contacts available in TB address book. If a contact in Outlook contains a certificate it is correctly synchronized to the DAV server (see tickets for more details) It is then downloaded to TB with SOGo. The certificate is not shown in the TB address book as the field is not part of the GUI. If the contact object is opened, not changed, and then closed again SOGo Connector uploads the contact again, but the KEY field is now falsely encoded. The corrupt vcf is accepted by SabreDAV (and SOGo, too, see SabreDAV ticket). As a result, SabreDAV (and SOGo) now server corrupt XML and CardDAV clients stop working. | ||||
| Steps To Reproduce | 1.) Use CalDAV client that supports certificates (KEY field) to upload a contact with correctly encoded KEY field to CardDAV server | ||||
| Additional Information | Outlook CalDAV Snychronizer ticket SabreDAV ticket | ||||
| Tags | No tags attached. | ||||
