Hi, I can answer most of your questions with no I believe. In the initial design of webical we excluded these matters to be able to use container authentication mechanisms. There is only one exception; the system administrator who has privileges to alter system wide configuration.
It would however surely be possible to add this to webical. But atm I don't really see your use case. Could you explain as what you are trying to accomplish? On 11/30/08 10:57 PM, raboof wrote: > I think it would be useful to be able to add users > - who cannot subscribe themselves to calendars > Why would you want to restrict users to subscribe to calendars? > - who can read, but not write (some) calendars > As the calendars are hosted externally and are not controlled by webical you can restrict access at the webdav layer if you want. I think that if you want to implement a strict access control in webical you would need a bit of an overhaul of the current design. The reasoning now is that all resources are controlled and regulated externally. This has the advantage that webical can be extermely pluggable, but the disadvantage that access control has to be implemented somewhere else. One way to do this is to couple webical and your webdav server to a central ldap server for authentication for example (this was our own business case). Thanks for your input, you're welcome to step in with more ideas if you like. Regards, Ivo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "webical-developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webical-developers?hl=en -~----------~----~----~----~------~----~------~--~---
