Until OXSE 6.14 rev 6 I was able to switch ENABLE_INTERNAL_USER_EDIT flag (in foldercache.properties) to FALSE in order to prevent users from modifying their personal vCard in the Global Address Book.
Furthermore, the context administrator was able to edit the folder permissions and change, for a restricted number of users, the "modify" right from "none" to "own" or "all".
With OXSE 6.14 rev 8, turning ENABLE_INTERNAL_USER_EDIT to FALSE has the same effect as before (all users, by default, cannot modify their personal vCard) but now, when the context administrator tries to edit folder permissions, the following error is displayed:
"Error: Only the folder visibility permission is allowed to be changed for Global address book in context 1. (FLD-0081, -125920749-379)".
Why this restriction has been implemented?
My requirement is to limit Global Address Book changes (user vCards) to a restricted number of OX users: with previous version, Global Address Book permissions are editable by the context administrator so I could implement this use case, but now I cannot customize those permissions.
Are you planning to support some kind of permission management on the Global Address Book?
Furthermore, the context administrator was able to edit the folder permissions and change, for a restricted number of users, the "modify" right from "none" to "own" or "all".
With OXSE 6.14 rev 8, turning ENABLE_INTERNAL_USER_EDIT to FALSE has the same effect as before (all users, by default, cannot modify their personal vCard) but now, when the context administrator tries to edit folder permissions, the following error is displayed:
"Error: Only the folder visibility permission is allowed to be changed for Global address book in context 1. (FLD-0081, -125920749-379)".
Why this restriction has been implemented?
My requirement is to limit Global Address Book changes (user vCards) to a restricted number of OX users: with previous version, Global Address Book permissions are editable by the context administrator so I could implement this use case, but now I cannot customize those permissions.
Are you planning to support some kind of permission management on the Global Address Book?
Comment