Opened 11 years ago
Per-user authentication and authorisation
|Reported by:||Lewis Baker||Owned by:||Lewis Baker|
The plugin currently uses a single Perforce user for all interaction with the Perforce server. This means that all Trac users are able to browse the repository and changesets as that user with no way of restricting a particular user's view of the repository.
It would be useful to be able to map a particular Trac user account to the equivalent Perforce user account and have all interaction with the Perforce server operate under that Perforce account. The user's view of the repository should be the same as that the user gets when using the
p4 command line tool.
The 2006.1 server supports a new
p4 protects command that could be used to query a particular user's access rights.
There are also issues to do with obtaining the user's Perforce password to login and managing the Perforce tickets.