Feature #2855
closed
Move Authetication Settings to Project Level
Added by James Byrne over 15 years ago.
Updated 5 months ago.
Description
Presently authentication settings are global for all projects contained in a Redmine instance. It would be useful to move all of this down to the project level.
To accommodate self-registration it might be useful to automatically create a new role having minimal privileges with each new project. Self registrations would be assigned this role by default.
- Status changed from New to Closed
You can define for each (private) project which users shall be able to see it. If a project is not public, only its explicit members are able to see or interact with it according to their respective roles in the project.
For public projects, in addition to the explicit members, all logged in users can also see and interact with the public project with the permissions of the special "Non-Memmer" role. You can also set any other role as the designated non-member role for each project.
If the admin of a Redmine installation does has enforced authentication, only logged in users can see and interact with any project. If force euthentication is disabled, public projects are visible to not logged in (anonymous) people with the permissions of the implicit "Anonymous" role. As before, you can set a different role for each project whioch shall be considered the anonymous role for the project.
As such, the global setting to enforce authentication merely adds another protection to Redmine instances where the Admin wants to make sure that no project data is accessible to non-authenticated people.
Also available in: Atom
PDF
Updated by