Rights based on title/description

[stonewareslord]

It seems that Radicale only has support for checking rights based on username or access URL (as can be seen in this function).

Since calendar URLs are randomly generated UUIDs, this seems to make it impossible to create, say, a shared calendar without modifying the rights file.

In the following examples, assume a rights file that includes:

[public-read]
user: .*
collection: .+-shared(\.ics)?$
permission: r

I would expect the user flow to be:

1. Create calendar named "public-calendar-shared"
2. The url returned is something like http://radicale.example.com/user/14371353-39d9-4728-bc64-3d9a0288d49b
3. Someone accesses the calendar url
4. The url points to a calendar with a name that matches the public-read right
5. Read access is granted

However, the flow seems to be:

1. Create a calendar named "public-calendar-shared" (this name does not actually matter, since it's never checked)
2. The url returned is something like http://radicale.example.com/user/e81180f5-a72a-4613-ace2-2fe70c9cdb7d
3. Someone accesses the calendar url
4. The url doesn't end in -shared and access is denied
5. The server administrator manually has to create a new role that matches user/e81180f5-a72a-4613-ace2-2fe70c9cdb7d and restarts the Radicale server
6. Someone re-accesses the calendar url
   1: Access is granted because the manual, administrator-added right

Is this not the process I should follow to share a collection?

If not, could the title be checked in the regular expression? Alternatively, a role could be added like:

[public-read]
user: .*
collection-description: .*\(\+shared\).*$
collection: .+
permission: r

And anything with (+shared) in the description would be public