Bearer auth backend causes problems with several dav clients

[nickvergessen]

The topic is getting way too much replies:
https://help.nextcloud.com/t/nc12-authentication-issue-with-cardav-caldav-and-sogo-connector/12924/

We need to find a way for this, so it doesn't break all the clients anymore.

cc @LukasReschke

[GieltjE]

#5092 Appears to be a duplicate or at least directly related.

[nickvergessen]

Yeah, see the link to the forum above for a temporary workaround

[LukasReschke]

Does reordering the auth mechanisms help or should we do something REALLY hacky and prevent the second Authenticate header?

Note that this really is more of a bug in the clients… but well, if apparently all clients implement such stuff incorrectly 🙈

I think the hacky approach might help us more :)

[nickvergessen]

Reordering doesn't seem to help, because the order is different on the dav/ endpoint, but many people also have problems on that one.

[LukasReschke]

K, we'll then just pretend to only do Basic Auth 🙈

[microglossum]

Thanks for bringing this in 12.0.1. When will this be released? Where can I find a release-plan for minor updates? The topic is quite important for me.
I found https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule and https://github.com/nextcloud/server/milestone/25 but those didn't help a lot.

[nickvergessen]

@Aehrraid you can also just fix it manually right now with:
https://help.nextcloud.com/t/nc12-authentication-issue-with-cardav-caldav-and-sogo-connector/12924/9

the "average" release cycle is 4weeks