Z-Push not creating users on CardDAV/CalDAV server (Baikal) with LDAP patch

[eduardomozart]

Describe the issue
Hello,
I've described this issue with details at YunoHost-Apps/baikal_ynh#110
Basically, a patched Bailkal can create a LDAP user on MySQL DB of Baikal on the fly using Apple Calendar and other programs, but not with Z-Push and MS-Outlook. It could be fixed by implementing the Principal Backend for LDAP at Bailkal, but Z-Push could request an OPTION or / before requesting PROPFIND to CalDAV, so the CalDAV server can create the LDAP user instead of assuming that the user already exists on Principal Backend. It would also make it work with other CardDAV/CalDAV server that uses other backends, like IMAP or Apache/NGINX, that offer no way to expose Principal Backend.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[matidau]

Hi @eduardomozart , user creation or problems with user creation isn't within the realm of Z-Push. In the scenario you provided, best practice set up for Z-Push is to use the LDAP backend as well as any others to ensure proper authentication. For this to work the user would already need to be created in LDAP, and as part of this user creation, the user should be created in Baikal (or Baikal uses LDAP).