[rt-users] Public read-only acccess to tickets

[James Chamberlain]

On Aug 3, 2005, at 12:18 PM, Thomas Sibley wrote:

> James Chamberlain wrote:
>
>> I was going to approach this problem at a lower level.  If I've  
>> got this right, the default ACLs that RT sets up (at least for  
>> MySQL and PostgreSQL) specify that RT should be allowed to select,  
>> insert, update, and delete.  If instead the ACLs were modified so  
>> that RT could only select, I think that would accomplish the  
>> goal.  I haven't set this up yet, so I don't yet know yet how RT  
>> will handle this.  Perhaps that's a question for the list.  This  
>> technique will require two RT installations sharing one db - one  
>> internal, which has full permissions and will run rt-mailgate; and  
>> the other external, which will only be allowed to view.
>>
>
> I'm not sure how RT will react to this.  For one, it won't be able  
> to store session information in the database, though it will still  
> want users to log in (unless you cut that part out).  I doubt it  
> will work as expected/desired, but have a go at it and see what  
> happens.  :)

Then perhaps it would work to give the external instance of RT full  
privileges on whichever tables are used for session information, but  
only select on all others?   I'm assuming this would be the  
"sessions" table, possibly "Users" - any others?

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20050803/f810d3db/attachment.htm>