I’m happy that it now works for you and will consider handling responses less strict (but I don’t know if and when, because that would change the sync logic again and at the moment, I don’t want to play around with it).
[Baïkal] After update to 0.9.0.3 login fails
-
Hello,
I have the problem that after update to 0.9.0.3 login fails. I get for my accounts a notification that loginname/password are wrong. I have no problems with other clients, so Baikal Server should not be the problem. I also retyped loginname/password in DAVdroid. TIA for help. I have a Nexus 5 with Cyanogenmod 12.1.
-
Hello,
@ulli45 said:
I have the problem that after update to 0.9.0.3 login fails. I get for my accounts a notification that loginname/password are wrong. I have no problems with other clients, so Baikal Server should not be the problem. I also retyped loginname/password in DAVdroid. TIA for help. I have a Nexus 5 with Cyanogenmod 12.1.
Did you disable preemptive auth. (see https://davdroid.bitfire.at/configuration)?
-
Hello rfc2822,
thanks for your fast answer. I disabled it, now it works! As described in your link, it is recommended to change Baïkal to Basic auth and use preemptive auth with HTTPS. I am not an expert in these things but do I have now a security problem? What happens if I change Baïkal to Basic auth? Little confused…Thanks a lot for your help!
-
@ulli45 said:
What happens if I change Baïkal to Basic auth? Little confused…
If you use TLS (https URLS): Basic is as secure as Digest, but easier and faster (and less error prone). There’s no reason to use Digest auth on HTTPS connections.
If you don’t use TLS (http URLs): use Digest auth to protect your credentials.
-
Great, thanks a lot. Yes, I use https. I just wanted to check that again, but I can’t find the settings to see/edit the URL. Isn’t it possible?
-
@ulli45 said:
Great, thanks a lot. Yes, I use https. I just wanted to check that again, but I can’t find the settings to see/edit the URL. Isn’t it possible?
You could see the URL if you would enable external logs and have a look at the log file. Or you just delete the account and add it again with https://.
-
OK, thanks a lot!