[p4] Restrict use of p4 user command
rajul.vora at commerceone.com
Mon Jan 31 10:05:24 PST 2000
I believe another way to restrict users from creating new users is to make
sure there is no 'user *' line in p4 protect. Ie. control all user access
via groups. We actually maintain a "alluser" group to simulate 'user *'.
> -----Original Message-----
> From: Ed Mack [mailto:edm at wrq.com]
> Sent: Thursday, January 27, 2000 9:21 AM
> To: 'heinz2 at llnl.gov'; Steve Cook
> Cc: 'perforce-user at perforce.com'
> Subject: RE: [p4] Restrict use of p4 user command
> We simply fill up the empty license slots with dummy users (e.g.
> zz-p4user-1, zz-
> p4user-2, etc.), so no one can accidentally create a new
> user. When a new
> person needs to be added, we superusers get a called--because
> they get the
> error "license quota exceeded!"--and we simply delete a dummy
> user and set
> up the new one.
> > -----Original Message-----
> > From: Ines Heinz [mailto:heinz2 at llnl.gov]
> > Sent: Thursday, January 27, 2000 8:24 AM
> > To: Steve Cook
> > Cc: 'perforce-user at perforce.com'
> > Subject: Re: [p4] Restrict use of p4 user command
> > While this wouldn't prevent users from adding new users, you
> > could write a script that would delete all unknown users from
> > the database. The demon would wake up every so often, query
> > p4 for a list of users, and delete any users not on the
> > accepted list. The other way to do it is to add fake usernames
> > so that you are "using" all your licenses. Then p4 will tell
> > the person trying to add a user that all user licenses are
> > in use and they can't access the db.
> > Yeah, they're hacks, but there isn't any good way via perforce
> > to do it. The other annoyance I have is that any user can
> > delete a branch specification. Granted, this doesn't delete
> > the branch. However, it causes problems for my users when
> > they try to integrate using the -b option.
> > Ines
> > Steve Cook wrote:
> > >
> > > Is there any way to prevent users from adding new users?
> > Although I have
> > > defined all the users already, occasionally a user will run
> > p4win in NT with
> > > a slightly different userid and somehow end up creating a
> > new user. As a
> > > result the same person is listed more than once as a user
> > with slight
> > > variations in spelling or capitalization in user name.
> > >
> > > It would be nice to be able to use p4 protect to restrict a
> > group's access
> > > to a specific command.
> > >
> > > Any ideas?
> > >
> > > Stephen A. Cook
> > > Release Engineering
> > >
> > > CyberGuard Corporation
> > > scook at cyberguard.com
> > > Office: (954) 958-3900 x3238
> > > Cell phone: (561) 901-3070
> > >
> > > _______________________________________________
> > > perforce-user mailing list - perforce-user at perforce.com
> > > http://maillist.perforce.com/mailman/listinfo/perforce-user
> > _______________________________________________
> > perforce-user mailing list - perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user