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

Attendees can't see busy slots #3149

Closed
st3iny opened this issue Jun 4, 2021 · 6 comments · Fixed by #5451
Closed

Attendees can't see busy slots #3149

st3iny opened this issue Jun 4, 2021 · 6 comments · Fixed by #5451
Assignees
Labels
3. to review Waiting for reviews bug Feature: Scheduling Anything around scheduling meetings, free-busy, resources, attendees and so on

Comments

@st3iny
Copy link
Member

st3iny commented Jun 4, 2021

Steps to reproduce

  1. Create event and invite someone.
  2. Have the other person click on Show busy times in the sidebar.

Expected behaviour

The invited person should either see free/busy slots of attendees or should not be able to click the Show busy times button at all.

Actual behaviour

No busy slots will be shown in the modal. The console logs the same error twice:

Request:

XHRPOSThttp://localhost/remote.php/dav/calendars/admin/outbox/
[HTTP/1.1 403 Forbidden 351ms]

Response:

<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:exception>Sabre\DAV\Exception\Forbidden</s:exception>
  <s:message>The organizer in the request did not match any of the addresses for the owner of this inbox</s:message>
</d:error>

Versions

Calendar app version: master
Nextcloud Version: stable21

@st3iny st3iny added bug 0. to triage Pending approval or rejection labels Jun 4, 2021
@st3iny st3iny changed the title Attendees can't see free busy slots Attendees can't see busy slots Jun 4, 2021
@ChristophWurst ChristophWurst added Feature: Scheduling Anything around scheduling meetings, free-busy, resources, attendees and so on 1. to develop Accepted and waiting to be taken care of and removed 0. to triage Pending approval or rejection labels Jun 4, 2021
@ChristophWurst
Copy link
Member

I can reproduce. Would be interesting to see if this work in Thunderbird, just to find out if Calendar is doing it wrong.

@tcitworld
Copy link
Member

Could you post the request payload as well?

@ChristophWurst
Copy link
Member

BEGIN:VCALENDAR
PRODID:-//IDN nextcloud.com//Calendar app 2.2.1//EN
CALSCALE:GREGORIAN
VERSION:2.0
METHOD:REQUEST
BEGIN:VFREEBUSY
DTSTAMP:20210604T115239Z
UID:e659ed46-ea7b-420f-8fac-2aab0733d9f5
DTSTART:20210531T220000Z
DTEND:20210601T220000Z
ORGANIZER;CN=Org:mailto:org@domain.tld
ATTENDEE;CN=Att1:mailto:att1@domain.tld
ATTENDEE;CN=Att2:mailto:att2@domain.tld
END:VFREEBUSY
END:VCALENDAR

@tcitworld
Copy link
Member

And is org@domain.tld the email for the user admin, just to be sure?

@st3iny
Copy link
Member Author

st3iny commented Jun 4, 2021

The organizer of a free busy request should be the owner of the inbox but we always send the organizer of the event regardless of the querying user. I think that's why the request always fails for attendees.

@provokateurin
Copy link
Member

Would it be possible to disable the busy times functionality for these cases? I was thinking busy times were broken because I always checked on an existing event (looking to reschedule it) but then the busy times were always empty. Took me a while to realize that I need to check on a new event...

@ChristophWurst ChristophWurst added 2. developing Work in progress and removed 1. to develop Accepted and waiting to be taken care of labels Sep 5, 2023
@ChristophWurst ChristophWurst self-assigned this Sep 5, 2023
@ChristophWurst ChristophWurst added 3. to review Waiting for reviews and removed 2. developing Work in progress labels Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug Feature: Scheduling Anything around scheduling meetings, free-busy, resources, attendees and so on
Projects
Development

Successfully merging a pull request may close this issue.

4 participants