Carddav sync error - Sogo

[EmreTekne]

Dear developers,

Were trying to use linphone also as a contact list provider and we saw that as of version 6.0.0 there is a Carddav option.
There is a demo site from Sogo we want to use as solution to host the contact list and by synchronizing it with a client to the native client list or client list in the SIP client.

We did not manage to establish a connection via the Linphone app.
Here is a log file: https://files.linephone.org/http-file-transfer/tmp/67e6bc903ed5e_e5b8677d24e1d296aad5.gz

I also added the log file.

The demo site: https://demo.sogo.nu/SOGo
Accountname: sogo1
Password: sogo

If we use a different app called "Davx5" we can establish it with no issues but we dont want to many 3rd party apps.
Please help us.

With kind regards from the Netherlands :).

[EmreTekne]

log.txt

[Viish]

Hi @EmreTekne,

Thanks for the logs, I'll try to replicate on my site and provide a fix for that.

Cheers,

[Viish]

Hi @EmreTekne,

I understood what happens: SOGo asks for Basic authentication, but the Auth Info stored in Linphone won't work as the password is removed and replaced by HA1 for safety purposes, which renders the app unable to do Basic auth.

Could you enable Digest auth on the server?

Cheers,

[Viish]

As a workaround, you can edit this file https://gitlab.linphone.org/BC/public/linphone-android/-/blob/master/app/src/main/java/org/linphone/ui/main/settings/viewmodel/CardDavViewModel.kt#L201
and replace

Log.i("$TAG Adding auth info with username [$user]")
val authInfo = Factory.instance().createAuthInfo(
    user,
    null,
    pwd,
    null,
    authRealm,
    null
)
core.addAuthInfo(authInfo)

by

val authInfo = Factory.instance().createAuthInfo(
    user,
    null,
    pwd,
    null,
    authRealm,
    null,
    "BASIC"
)
core.addAuthInfo(authInfo)

[EmreTekne]

The Sogo site is a demo site, we are not the full admin.
So we can not make adjustments, however we can make adjustments on the phone side. I will try to change the file on the phone.
However is it not possible to configure auth method input in the app? That would be very helpfull, we are still investigating to host our own Sogo site but we want to test every function before making this call.

[Viish]

@EmreTekne you can use remote provisioning (see https://wiki.linphone.org/xwiki/wiki/public/view/Lib/Features/Remote%20Provisioning/) to configure

[sip]
store_ha1_passwd=0

, that will allow the client to do BASIC authentication.

[Viish]

You might want to try setting the realm field of the CardDAV form empty, it may also work.

[floi]

I'm having the same problem with a CardDav provider that only seems to support basic authentication (NextCloud). I'm getting closer but it's still not working:

After both setting store_ha1_passwd=0 in the linphonerc and using the basic realm sent by NextCloud in the WWW-Authenticate header for the authentication realm field in the Linphone GUI, I was able to synchronize the address book.

However, the contacts don't show up under contacts (despite being in the linphone.db) immediately after synchronization. When I restart Linphone it segfaults:

QML debugging is enabled. Only use this in a safe environment.
 2025-05-26 14:29:50:528 [app] DEBUG [Main] Setting ShareOpenGLContexts
 2025-05-26 14:29:50:528 [app] DEBUG [Main] Disabling VSync
 2025-05-26 14:29:50:531 [app] DEBUG [Main] Disabling QML disk cache
 2025-05-26 14:29:50:531 [app] DEBUG [Main] Setting application to UTF8
 2025-05-26 14:29:50:531 [app] DEBUG [Main] Creating application
 2025-05-26 14:29:50:659 [app] MESSAGE Loading Fonts
 2025-05-26 14:29:50:741 [app] MESSAGE Font families loaded:
         Noto Sans
        Noto Sans Light
        Noto Sans ExtraBold
        Noto Sans ExtraLight
        Noto Sans Black
        Noto Sans Thin
        Noto Sans Medium
        Noto Sans SemiBold
        OpenMoji Color
        OpenMoji
 2025-05-26 14:29:50:742 [app] MESSAGE [App]: Starting Thread
 2025-05-26 14:29:50:742 [app] MESSAGE Thread is running
 2025-05-26 14:29:50:854 [app] DEBUG installed sys locale "en_US"
 2025-05-26 14:29:50:854 [app] MESSAGE [App]: Display server : xcb
 2025-05-26 14:29:50:854 [app] MESSAGE Starting application Linphone (bin: linphone). Version:6.0.0-CallEdition Os:ubuntu/24.04 Qt:6.9.0
 2025-05-26 14:29:50:854 [app] DEBUG binpath= "/tmp/.mount_LinphosdDbtq/usr/bin/linphone"
 2025-05-26 14:29:50:854 [app] DEBUG exec path autostart set appimage= "/home/floi/Downloads/Linphone-6.0.0-CallEdition-x86_64.AppImage"
 2025-05-26 14:29:50:854 [app] DEBUG [Main] Initializing core for primary application
[1]    39186 segmentation fault (core dumped)  Downloads/Linphone-6.0.0-CallEdition-x86_64.AppImage

[Viish]

Hi @floi,

Please open this issue in https://github.com/BelledonneCommunications/linphone-desktop as it concernes linphone-desktop app, and attach the crash stack trace if you can.

Thanks in advance.

[petervnv]

Hi @Viish,

I am also playing around with carddav in linphone and I am seeing a different problem when trying to sync with a remote server I control. In my server, the auth service is handled by a script I wrote that handles digest authentication, but I kept getting login errors and I suddenly realised something. In my sip auth section I use SHA256, but it seems that Linphone's carddav implementation still uses older MD5. Is that correct? Where in the 6.0 code can I see the carddav algo and digest auth in general? I see you posted this link earlier in March but I don't see any algo parameters there. https://gitlab.linphone.org/BC/public/linphone-android/-/blob/master/app/src/main/java/org/linphone/ui/main/settings/viewmodel/CardDavViewModel.kt#L201

Also, on a related note, which carddav server do you use that works well with Linphone? It seems the only open source options out there are radicale (no support for digest auth though ): and baikal. Before I spin up a new baikal server to test (I believe Baikal supports digest auth) can you confirm it works with that server?

Cheers,
Peter

[Viish]

Hi @petervnv,

Yes we use Baikal for our tests and it does support Digest auth.
Regarding SHA256/MD5 yes there's no setting as an AuthInfo created with no specific algorithm will use the one required by the server in the 401 Unauthorized.

Cheers,

[petervnv]

Hi @Viish,

Thanks for the quick reply and for confirming that Baikal works well with Linphone!

Are you sure the client replies with the algo sent by the server?
Strange that I always see Linphone replying with MD5 ha1. I see the reply after the server challenge is always 32hex even though the server is explicitly requesting sha-256:

                                                                                                HTTP/1.1 401 Unauthorized
                                                                                                Content-Length: 0
                                                                                                Content-Type: text/html; charset=utf-8
                                                                                                Date: Sat, 01 Nov 2025 12:40:33 GMT
                                                                                                Server: Werkzeug/3.1.3 Python/3.11.14
                                                                                                Vary: Cookie
                                                                                                Www-Authenticate: Digest realm="my.domain", qop="auth", nonce="MTc2MjAwMDgzMzplOTA2MDlkMGM3MDcyZmNh", algorithm="SHA-256", stale=false, domain="/ /radicale", opaque="d662f8f0ea650f96"

and our reply is missing the algo parameter, thus it defaults to MD5 regardless of what the server requests:

channel [0x78b53b0ead20]: message sent to [TLS://contacts.my.domain:443], size: [555] bytes
                                                                                                    PROPFIND / HTTP/1.1
                                                                                                    User-Agent: LinphoneAndroid/6.0.19 (sdk_gphone64_x86_64) LinphoneSDK/5.4.50-pre.1+4c8eae6d7a (release/5.4)
                                                                                                    Depth: 0
                                                                                                    Content-Type: application/xml;charset=utf-8
                                                                                                    Content-Length: 85
                                                                                                    Host: contacts.my.domain
                                                                                                    Authorization: Digest realm="my.domain", nonce="MTc2MjAwMDgzMzplOTA2MDlkMGM3MDcyZmNh", opaque="d662f8f0ea650f96", username="1007", response="535c2719b25a88f316bbe45b2f02e41e", cnonce="oDRIp2rKMBl1eUjY", nc=00000001, qop=auth, uri="/"

Can you please point to where in the code the AuthInfo for CardDav is created so I can force sha-256 from the client side?

Cheers,
Peter

[Viish]

Hi @petervnv,

Can you please point to where in the code the AuthInfo for CardDav is created so I can force sha-256 from the client side?

Right here: https://gitlab.linphone.org/BC/public/linphone-android/-/blob/master/app/src/main/java/org/linphone/ui/main/settings/viewmodel/CardDavViewModel.kt#L219

Could you send me the full logs please? It's weird the SDK uses a MD5 auth info even if SHA-256 is requested.
Thanks in advance.

Cheers,