I’m trying to use the “Login with email” way to connect to my owncloud 8 server, let’s say with “firstname.lastname@example.org” where “name” is the user and “domain.tld” the domain where the .well_known redirections can be found.
DAVDroid (0.7 from F-Droid) reports
Erreur HTTP : 401 Unauthorized"
while my owncloud 8 logs this warning:
Login failed: ‘email@example.com’ (Remote IP: ‘xxx.xxx.xxx.xxx’, X-Forwarded-For: ‘’)
So DAVDroid tries to login only with the full email and unfortunately owncloud only accepts logins with the user name.
Is it possible to implement some sort of fallback to try to login with only the local part of the email?
In https://tools.ietf.org/html/rfc6764#page-7 point 4, I found this:
When a user identifier is required, clients MUST first use the “mailbox” portion of the calendar user address provided by the user in the case of a “mailto:” address and, if that results in an authentication failure, SHOULD fall back to using the “local-part” extracted from the “mailto:” address.
So I assume that DAVDroid SHOULD try to login with my “name”.
Is it possible to add this fallback?
By the way, this rfc also points to https://tools.ietf.org/html/rfc6764#section-7 that also says:
CalDAV or CardDAV servers SHOULD be configured to allow authentication with calendar user addresses (just taking the “mailbox” portion of any “mailto:” URI) or email addresses respectively, or with “user identifiers” extracted from them.
So I will also check owncloud side if I can do something to make it accept email logins. https://github.com/owncloud/core/issues/2927 seems to be related, but it’s quite old …