Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS calendar: Can't search for delegates to add #17053

Closed
labor4 opened this issue Sep 8, 2019 · 9 comments · Fixed by #36800
Closed

macOS calendar: Can't search for delegates to add #17053

labor4 opened this issue Sep 8, 2019 · 9 comments · Fixed by #36800
Labels
1. to develop Accepted and waiting to be taken care of enhancement low

Comments

@labor4
Copy link
Contributor

labor4 commented Sep 8, 2019

I'm trying to test the new proxy delegation feature in NC17b3 with iCal Mojave Macos. No success.

According to sabredav there are sub-principals needed. Do I need to activate/configure something in NC in advance?

Following are apache2 access logs. No entries in apache2 error log. No entries in NC log.

iCal request which wants to display the current access ("Which accounts do I have access to?")
1.2.3.4 - - [08/Sep/2019:02:53:53 +0200] "REPORT /nc/11/remote.php/dav/principals/users/MYUSER/calendar-proxy-write/ HTTP/1.1" 401 450 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1) 1.2.3.4 - - [08/Sep/2019:02:53:53 +0200] "REPORT /nc/11/remote.php/dav/principals/users/MYUSER/calendar-proxy-write/ HTTP/1.1" 207 537 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1) 1.2.3.4 - - [08/Sep/2019:02:53:53 +0200] "REPORT /nc/11/remote.php/dav/principals/users/MYUSER/calendar-proxy-read/ HTTP/1.1" 401 450 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1) 1.2.3.4 - - [08/Sep/2019:02:53:53 +0200] "REPORT /nc/11/remote.php/dav/principals/users/MYUSER/calendar-proxy-read/ HTTP/1.1" 207 536 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1)

iCal request which wants to autocomplete/search against existing user, to share my account to (Try to set up new)
1.2.3.4 - - [08/Sep/2019:02:55:38 +0200] "REPORT /nc/11/remote.php/dav/principals/calendar-resources/ HTTP/1.1" 401 450 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1) 1.2.3.4 - - [08/Sep/2019:02:55:38 +0200] "REPORT /nc/11/remote.php/dav/principals/calendar-resources/ HTTP/1.1" 207 282 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1) 1.2.3.4 - - [08/Sep/2019:02:55:38 +0200] "REPORT /nc/11/remote.php/dav/principals/calendar-resources/ HTTP/1.1" 207 282 "-" "Mac+OS+X/10.14.6 (18G87) CalendarAgent/416.5.1" (proxy:10.24.62.1)

via iCal/Calendar Macos

  • Tested against an older user
  • Tested AGAINST a fresh user from an old one (fresh is NC17b3 created)
  • Tested FROM a fresh user against an old one.

Expected
Some kind of content feedback/ index/ search result.

Actual
Error displayed by iCal: roughly translated, "You cannot give SEARCHUSER access to your account because SEARCHUSER could not be found on server".

@labor4 labor4 added bug 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Sep 8, 2019
@georgehrke
Copy link
Member

Sadly Nextcloud will need further patches for macOS, because macOS is not implementing a couple of things correctly. (Principal property search for multiple principal collections and proper handling of response code 204 for PropPatch)

The calendar app will introduce its own configuration interface for delegates.

@georgehrke georgehrke added 1. to develop Accepted and waiting to be taken care of low and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Sep 8, 2019
@georgehrke georgehrke added this to the Nextcloud 18 milestone Sep 8, 2019
@georgehrke georgehrke changed the title N17b3: failing with delegation/calendar-proxy from iCal Mojave macOS calendar: Can't search for delegates to add Sep 8, 2019
@georgehrke georgehrke added enhancement and removed bug labels Sep 8, 2019
@labor4
Copy link
Contributor Author

labor4 commented Sep 8, 2019

ah the old macos caldav special case. why am i not surprised.
thanks a lot!

@ChristophWurst
Copy link
Member

georgehrke added this to the Nextcloud 18 milestone on 8 Sep

@georgehrke please check if this is doable for 18 or if we should move to 19 :)

@rullzer rullzer removed this from the Nextcloud 18 milestone Dec 19, 2019
@georgehrke
Copy link
Member

Not doable for 18 anymore. For whatever reason, macOS calendar ever only searches one out of multiple principal collections. This would require further debugging.

My current approach for this would be adding a special plugin that checks for the macOS calendar user agent and automatically sets "apply-to-principal-collection-set" to true. That change might very well break other things for macOS, so we should do it later and properly test it.

@labor4
Copy link
Contributor Author

labor4 commented Jan 5, 2020

didn't they do the same with contacts?
i think there was never a multi-abook-same-account capability on macos even though i think it was the carddav concept.

@georgehrke
Copy link
Member

i think there was never a multi-abook-same-account capability on macos even though i think it was the carddav concept.

As far as I'm aware of there is a similar issue with calendar-homes and address-book-homes. CalDAV and CardDAV allow multiple homes, macOS ever only picks one.

@labor4
Copy link
Contributor Author

labor4 commented Apr 2, 2020

may I ask if this is planned for NC 19?

@georgehrke
Copy link
Member

This is not planned for a release any time soon, I don’t have time for it.
If someone wants to contribute a PR I’d be happy to give pointers

@rotdrop
Copy link
Contributor

rotdrop commented Feb 21, 2023

This is not planned for a release any time soon, I don’t have time for it. If someone wants to contribute a PR I’d be happy to give pointers

#36800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of enhancement low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants