[rt-users] unprivileged users in ticket owner list
Ruslan U. Zakirov
Ruslan.Zakirov at miet.ru
Mon Jul 11 17:51:16 EDT 2005
Jon Daley wrote:
> On Mon, 11 Jul 2005, Alan Sparks wrote:
>
>>> One of the bugs in RT 3.2.X (and perhaps carried over to RT 3.4.X) is
>>> that if you give rights or group membership to a user, then uncheck the
>>> "Let this user be granted rights" checkbox, RT does _not_ strip that
>>> user's rights or group membership.
>>
>>
>> Bummer. Disabling a user should suspend all rights for that user.
>> Wonder
>> if that's been filed as a bug?
AFAIK this is "problem" of all(even 3.4.x, but may be it has some
"fixes") RT versions. You can block access to RT only by disabling user.
IMO best approach is grant rights only to groups and control access by
adding/deleting users to/from groups. After you know user has rights you
want, you can use privileged status to choose WebUI(fullfeatured or self
service). If you want block user at all then disable his record.
>
>
> Cannot reproduce in 3.4.2, disabling and removing privileges works
> as expected. (though I am getting a "no connection to syslog available
> at /usr/share/perl5/Log/Dispatch/Syslog.pm line 77" when trying to login
> as a disabled user. The entry is logged appropriately)
I think "no connection to syslog" is unrelated to user status. This
error is documented on the wiki. Are you sure that you don't get this
error in other situations?
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Be sure to check out the RT Wiki at http://wiki.bestpractical.com
>
More information about the rt-users
mailing list