Rimez and others,

PrivateTicketsPlugin-extensions seems to point in a good direction.
Maybe we can change it in the way we want? Unfortunately I'm not
familiar with the trac-api.

PrivateTicketsPlugin defines a class PrivateTicketsSystem which
implements
IPermissionRequestor and has therefore a method
check_permission(self, action, username, resource, perm):

- Is this method also called for each comment/attachement?
- if so: What is in this case the value for resource.realm?
          What is the value for resource.realm?

Can anybody help?

Bye
Benedikt


On 6 Apr., 08:09, rimez <[EMAIL PROTECTED]> wrote:
> I would be interested in this as well.
>
> I found a plugin called "PrivateTicketsPlugin" which I hope may point
> us in the right direction.
>
> Can someone provide more feedback on doing this?
>
> Cheers,
> rimez
>
> http://trac-hacks.org/wiki/PrivateTicketsPlugin
>
> On Apr 4, 2:41 pm, "Benedikt.Rothe" <[EMAIL PROTECTED]>
> wrote:
>
> > Hi
>
> > We use trac for software-bugtracking. External customers can use our
> > trac-instance for creating bugs, comments, uploading attachments and
> > to view tickets of other customers.
>
> > Often customers upload data to enable us to reproduce a bug. In some
> > cases this data is confidental and should not be visible to other
> > external customers.
>
> > Is it possible to restrict reading-access for these attachments, such
> > that only members of the
> > developer-group can see these attachements?
>
> > Similar problem: Developers might want to add comments which shouldn't
> > be visible by external customers, since these comments are pure
> > implementation-details.
>
> > Thanks
> > Benedikt

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to