[p4] Using p4 protect to create a "public" user

[Quanah Gibson-Mount]

--On Wednesday, October 10, 2007 7:40 PM -0700 Quanah Gibson-Mount 
<quanah at zimbra.com> wrote:

> Hi,
>
> I'm trying to set it up so I can have a user named "public" read just one
> particular part of the perforce tree.  I've got this mostly working,
> except  for three issues.
>
> (1) The user can change their password.  Since I want to make this user
> generally available, I need that capability blocked.

It looks like setting up external auth, and then making it so the user 
can't change the password there (LDAP in my case) would solve this issue.

> (2) The user can see the change lists for all branches (p4 changes -i -l
> is  particularly problematic).  How can I limit it so that p4 changes
> only  shows those changes in the view it is allowed to see?

This one so far doesn't seem solvable.  Anyone have ideas on it?

> (3) I'd like it so that the user cannot change the P4CLIENT view it uses
> (currently public-view).


This was solved via a trigger.  Thanks for the pointer Oren.:)

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration