Changes between Initial Version and Version 1 of SecureTicketsPlugin

Timestamp:

Dec 21, 2010, 9:45:32 PM (13 years ago)

Author:

Rob Guttman

Comment:

New hack SecureTicketsPlugin, created by robguttman

SecureTicketsPlugin

@@ +1 @@
+[[PageOutline(2-5,Contents,pullout)]]
+
+= Adds ticket security policy based on component =
+
+== Description ==
+
+This plugin was heavily inspired by cboos' [http://trac.edgewall.org/browser/trunk/sample-plugins/permissions/vulnerability_tickets.py vulnerability tickets] policy plugin.
+
+The authz policy mechanism provides fine-grained permissions for wiki pages.  This plugin attempts to provide fine-grained permissions for tickets segmented by component.  Specifically, unless a user has SECURE_TICKET_VIEW permissions, they will only be able to see tickets of public components.
+
+== Bugs/Feature Requests == 
+
+Existing bugs and feature requests for SecureTicketsPlugin are 
+[report:9?COMPONENT=SecureTicketsPlugin here].
+
+If you have any issues, create a 
+[http://trac-hacks.org/newticket?component=SecureTicketsPlugin&owner=robguttman new ticket].
+
+== Download ==
+
+Download the zipped source from [download:secureticketsplugin here].
+
+== Source ==
+
+You can check out SecureTicketsPlugin from [http://trac-hacks.org/svn/secureticketsplugin here] using Subversion, or [source:secureticketsplugin browse the source] with Trac.
+
+== Example ==
+
+An example is if you have a customer account team who create and need full access to tickets with a 'customer' component but should not have access to any other tickets.  The {{{trac.ini}}} file would look like this:
+
+{{{
+[components]
+securetickets.* = enabled
+
+...
+
+[securetickets]
+public_components = customer
+
+...
+
+[trac]
+permission_policies = SecureTicketsPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
+}}}
+
+
+== Recent Changes ==
+
+[[ChangeLog(secureticketsplugin, 3)]]
+
+== Author/Contributors ==
+
+'''Author:''' [wiki:robguttman] [[BR]]
+'''Maintainer:''' [wiki:robguttman] [[BR]]
+'''Contributors:'''