CALDAV synchronization

[sysadminpower2019]

The open web calendar should act as a CAL DAV client and synchronize with the cal dav server (radicale, baikal, sabre, etc) on a regular basis and update the events displayed on the calendar.

The open web calendar should also support encrypted authentication via username / password or other methods.

here is an example from of how to build a caldav client

https://sabre.io/dav/building-a-caldav-client/

---

We're using Polar.sh so you can upvote and help fund this issue. We receive the funding once the issue is completed & confirmed by you. Thank you in advance for helping prioritize & fund our work.

[niccokunzmann]

I found this: https://caldav.readthedocs.io/en/latest/caldav/objects.html#caldav.objects.CalendarObjectResource.expand_rrule

We should be able to do this:

• [ ] integrate a caldav type of URL - would caldav:// be ok? How would you imagine the user interface?
• [ ] Add a way to encrypt username+password. This can be done with a server secret and a random prefix so that you can not know if username and password are the same. https://ENC-BASE32DATA@url would be what it looks like in the URL, the. But clear text username+password urls should also work.
  • [ ] add username field behind the url
  • [ ] add password field behind the url
  • [ ] the url should be encrypted in the calendar specification and URL
  • [ ] add an environment variable with the password to decrypt on the server

Help needed

In order to develop this, I need access to a caldav server, some events, username+password. If this is there, I can write tests to make sure that the integration works.

[sysadminpower2019]

https://hilfe.udmedia.de/sonstige-themen/kalender-synchronisation-caldav/einrichtung-der-kalender-synchronisation-in-android-am-beispiel-der-app-davx5/

Here is a website with an example of how to connect a caldav address with an android client. It uses the normal http:// protocol address. This could be configured instead directly via text settings in the open calendar.

I am sure you could send the username and password information through the open calendar configuration instead of doing so directly in the link. As you can see this is how it is often implemented in other clients. How this is done exactly I don't know. Sadly, I am not a Dev

I would be happy to provide you with access to a server with a caldav server to test this in exchange for moving forward with the project.

[niccokunzmann]

I have anextcloud server. I think that means I have access to caldav.

[sysadminpower2019]

https://help.nextcloud.com/t/how-to-connect-to-caldav-server/32981/2

that should be the information needed for the caldav server

On Thu, Apr 13, 2023 at 8:02 PM Nicco Kunzmann @.***> wrote:

I have anextcloud server. I think that means I have access to caldav.

— Reply to this email directly, view it on GitHub https://github.com/niccokunzmann/open-web-calendar/issues/189#issuecomment-1507398719, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWXABWKLKPFPVY344MCNZ3XBA5RVANCNFSM6AAAAAAWZJZ7R4 . You are receiving this because you authored the thread.Message ID: @.***>

[sysadminpower2019]

Is there anything else I can do to help this along?

[niccokunzmann]

From my perspective, the issue is very clearly explained. Implementation is possible.

For open-source projects, there are roughly these ways that you can go now: Work on it yourself, get someone else to work on it (e.g. through payment) or wait until someone does it.

As I am interested lately in how to sustainably fund open-source projects, I am happy to talk about that, too. I am working on this in my free time usually. Contributions in all forms should be easy, so I make it open-source, document it, add a translation platform. I hope to make a software that is welcoming and has a low barrier for contribution.

Which way would you like to explore?