27 Mar
2009
27 Mar
'09
5:29 p.m.
hel-o wrote:
Hi,
use case would be, that any action a local user might want to do that needs programming
rights is not possible (using codes, macros, applications (Import Export Application) from
the code zone or creating own scripts using Velocity). And i would not like to grant every
user who needs programming rights, because he wants to do one of the things mentioned
above a global account.
Note that unlike all the other rights, programming does not apply to the
current user, but to the user that last saved the document.
Also, as Vincent said, most of the API is public and runs without
programming rights.
For me it is not that much of a problem, because i
have also an global account and i really understand your concerns about security. But its
also limiting the abilities of a virtual wiki environment.
But what i get from what your saying is, that its not possible to restrict the
programming rights for a local user only to his virtual wiki.
No, because you get access to internal classes that control the site.
The public API is obeying access rights, but with programming rights you
can go past them, inside our Java SPI.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/