F@lk said:
You're talking about SimpleMultiProjectPlugin
In that track ticket, yes, I see that is covers SimpleMultiProjectPlugin. If I understand correctly, that plugin is used when one wants multiple projects within one Trac environment. Sorry for posting to that ticket. That is not my scenario (as long as I understand correctly!)
a) authentication prior to/at the project listing page
b) checking permission for each project by reading their Trac db for every access to the project listing
For (a), yes I have authentication before any entry into the Trac pages.
For (b), yes, this is what I think needs to be done in my case. I can read/write code, I am just new to Trac/mod_python/Genshi... so pointers about how to patch things are welcome so that this can get done.
As your boss or yourself, what it is really worth.
Umm... yes, this feature is really worth it for me/us. Nothing about projects should be shown to a user without at least WIKI_VIEW privilege in the Trac environment under consideration. I am currently ok if a user can guess a project's URL and a WIKI_VIEW access denied message is shown, but I am not ok if a user sees all projects in the "Available Projects" list because then they learn about the existence of a project which we want to make "harder than easy to do" :)
Thanks for the suggestion. Perhaps in the future this could be an option, but I just want to restrict the list in "Available Projects". Mainly because once a user has selected a project to work on, they will not usually need to easily move to another project. In any case, in my view, it is better to make it a "little bit hard" to move between projects so that users have to make an effort to make a mistake about which project they are working on :)
All suggestions/pointers/corrections definitely welcome! I'm quite stuck at this point...
Kindly,
AikidoGuy