[horde] Share calendar via "private address"
Michael J Rubinsky
mrubinsk at horde.org
Wed Dec 9 18:01:00 UTC 2015
Quoting Jan Schneider <jan at horde.org>:
> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>>>
>>>> Quoting Frank Richter <frank.richter at hrz.tu-chemnitz.de>:
>>>>
>>>>> Quoting Michael J Rubinsky:
>>>>>>
>>>>>> Quoting Frank Richter <frank.richter at hrz.tu-chemnitz.de>:
>>>>>>
>>>>>>> Hi,
>>>>>>> pardon me, if this is a FAQ:
>>>>>>>
>>>>>>> Is there a possibility to give read access on a Kronolith
>>>>>>> calendar via a URL without authentication?
>>>>>>> Like this "private address" in Google -
>>>>>>> https://www.google.com/calendar/ical/.../private-c0feb88c.../basic.ics
>>>>>>>
>>>>>>> ... and without giving access to everybody within Horde.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Frank
>>>>>>>
>>>>>>> --
>>>>>>> Frank Richter
>>>>>>>
>>>>>>> Chemnitz University of Technolgy, Germany
>>>>>>
>>>>>> https://bugs.horde.org/ticket/7775
>>>>>
>>>>> Hmm, I just don't know how to do this:
>>>>>
>>>>> just create a new share (it has a random id) and set perms to
>>>>> READ|EDIT|DELETE
>>>>>
>>>>> Is it settable via the GUI in Calendar - edit calendar ->
>>>>> Sharing - advanced sharing options? How?
>>>>
>>>> This is basically just saying to create a new publicly viewable
>>>> calendar. Those instructions were from long ago (Horde 3) and
>>>> were really just a hackish workaround and don't really make sense
>>>> now.
>>>
>>> I'm not sure why this shouldn't still work.
>>
>> I guess it would still work if you wanted to start with a brand new
>> calendar. I thought the question was rather related to giving
>> someone access to an existing calendar without the need for
>> authentication.
>
> Should still work, if you give all but SHOW (and maybe DELEGATE)
> permissions to guests, and if guest access to Kronolith in general
> is allowed. The only "issue" is with very old default calendars
> which used to have an id matching the user name, which is of course
> too easily guessable to be used as a private address.
True. Only thing missing from the Google implementation then is being
able to change the ID and/or regenerate it in the case you need to
revoke previous access to some.
--
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5751 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/horde/attachments/20151209/52ace09c/attachment.bin>
More information about the horde
mailing list