Hello Frank, The documentation has been fixed. A collateral effect of using SOGoURLEncryptionPassphrase is that logging also doesn't contain the user nameExactly, but this is the goal. You have to decrypt username with a script : - Base64 decode of a part of the url - AES 128 decode with the good passphrase
SOGo code : https://github.com/Alinto/sogo/blob/master/SoObjects/SOGo/NSString%2BCrypto.m#L447 Sebastien Le Jeudi, Juillet 11, 2024 10:22 CEST, "Frank Richter" (frank.rich...@hrz.tu-chemnitz.de) <users@sogo.nu> a écrit: Am 08.07.24 um 15:32 schrieb qhivert (qhiv...@alinto.eu): This is an error of the documentation the dav url does stay the same. Thanks for reporting ! Ok, good. A collateral effect of using SOGoURLEncryptionPassphrase is that logging also doesn't contain the user name Jul 11 10:19:26 sogod [266027]: 2001:638:… "POST /SOGo/so/K57spNOfGTAoEypS7fpGQQ--/Mail/0/folderINBOX/changes HTTP/1.1" 200 27/152 0.318 - - 0 - 15 That makes support for a user difficult. Any idea, how to map such URLs back to a user name? Frank-- Frank Richter, Chemnitz University of Technology, Germany
