|Version 1 (modified by 9 years ago) ( diff ),|
Extension Point : IPermissionStore
The active IPermissionStore implementation stores the permissions and group memberships explicitly granted to users and groups.
The TracPermissions system supports granting and revoking of action permissions and of hierarchical groups that bundle and inherit permissions per user. The IPermissionStore interface can be used to replace the storage mechanism for these granted permissions.
Note that to implicitly grant additional permissions to certain users automatically, it is not necessary to implement (or wrap) IPermissionStore. Implement IPermissionGroupProvider instead.
Only the permission_store configured in trac.ini will be used. The configured implementation will be called by the permissions system to grant, revoke and query permissions. This information is automatically cached and reused for some time.
Due to the complexity of implementing a full permission store backend, no simple example can be provided here.
|DefaultPermissionStore||Stores permissions and admin defined permission groups in the project environment's SQL database.|
In third-party plugins:
|th:SuperUserPlugin|| Wraps another (|
Additional Information and References
- Epydoc API Reference
- See also IPermissionGroupProvider, IPermissionPolicy, IPermissionRequestor
- Related tickets:
- Related mailing list topics: