Digest auth problem after updating from 4.5.16-ose to 4.5.17-ose

[nathanzachary]

Problem scope

• I'm sure that this is a DAVx⁵ problem.

App version

• I'm using the latest available DAVx⁵ version.

Android version and device/firmware type

Android 16 (LineageOS 23.2) on OnePlus 13

Steps to reproduce

1. Update from version 4.5.16-ose to version 4.5.17-ose
2. Attempt to sync calendars or contacts

Actual result

On version 4.5.16-ose, synchronising succeeds, but on version 4.5.17-ose it fails (without any changes made to the authentication settings).

Expected result

Synchronisation should succeed on version 4.5.17-ose as it did with version 4.5.16-ose given that there were no changes to authentication settings or credentials.

Further info

I have attached some sections from the davx5-log.txt with the following substitutions made (for scrubbing personal DAV information):

• MYSITE --> my DAV URL
• MYUSER --> my username for that DAV site
• MYACCOUNT --> for the account name in DAVx5

[nathanzachary]

davx5-log_scrubbed.txt

[gainfully4302]

Exact same problem here. Authentication failure immediately after the update.

[rfc2822]

Does it work when you set the server to Basic authentication? From the logs I see that you can Baikal, and as far as I know it's the only server that accepts only Digest by default. As far as I know, you can set it to Basic. Can you try that just to be sure that the problem is about Digest auth?

(Actually there's no benefit in using Digest compared to Basic.)

[nathanzachary]

I can certainly give that a try. @gainfully4302 do you also use Baïkal or Sabre for your DAV backend? If so, it could be specific to us. If not, I would guess that making such a change on my end will be ineffective.

[rfc2822]

I can confirm that on our test Baikal server:

• login/authentication does not work when server is set to Digest auth, but
• login/authentication does work when server is set to Basic auth.

So as a workaround, you can set the server to Basic auth until this is fixed. (I'd then leave it on Basic since there's no use in having Digest, at least not when you're using HTTPS, which you should do anyway.)

[englut]

Swapped my Baikal's setting WebDAV authentication type from digest to basic and it works again. Would love to keep digest though.

[rfc2822]

Would love to keep digest though.

Will try to fix it (it's complicated), see also bitfireAT/dav4jvm#198.

Just for interest (off-topic): why do you prefer Digest?

[englut]

Just for interest (off-topic): why do you prefer Digest?

digest is more secure as it adds another layer of encryption.