16 messages in com.perforce.perforce-user[p4] Restrict use of p4 user command| From | Sent On | Attachments |
|---|---|---|
| Steve Cook | 27 Jan 2000 07:28 | |
| Steve Cook | 27 Jan 2000 07:46 | |
| Ducharme, Gregory | 27 Jan 2000 07:47 | |
| Robert Cowham | 27 Jan 2000 07:54 | |
| Ducharme, Gregory | 27 Jan 2000 07:54 | |
| Ducharme, Gregory | 27 Jan 2000 07:55 | |
| Chuck Karish | 27 Jan 2000 08:07 | |
| Ines Heinz | 27 Jan 2000 08:23 | |
| Dave Lewis | 27 Jan 2000 08:24 | |
| Robert Cowham | 27 Jan 2000 08:33 | |
| Michael Graff | 27 Jan 2000 08:42 | |
| Dave Lewis | 27 Jan 2000 08:49 | |
| Ed Mack | 27 Jan 2000 09:21 | |
| Ines Heinz | 27 Jan 2000 09:23 | |
| Scott Blachowicz | 31 Jan 2000 09:04 | |
| Rajul Vora | 31 Jan 2000 10:05 |
| Subject: | [p4] Restrict use of p4 user command |
|---|---|
| From: | Robert Cowham (rob...@vaccaperna.co.uk) |
| Date: | 01/27/2000 08:33:16 AM |
| List: | com.perforce.perforce-user |
It doesn't remove any current duff users, but it does stop a user running the p4 user command and creating a new non existent user which is not part of the alluser group.
See following test done with the 2 user free licence:
------- Group: allusers Users: robert -------- Protections: write group alluser * //... super user robert * //...
E:\Robert>set p4user=robert
E:\Robert>p4 protect Protections not changed.
E:\Robert>p4 users robert <robert at lodestone> (robert) accessed 2000/01/27
E:\Robert>p4 user User robert not changed.
E:\Robert>set p4user=chuck
E:\Robert>p4 user You don't have permission for this operation.
E:\Robert>set p4user=Robert Note different case
E:\Robert>p4 user You don't have permission for this operation.
QED!
Robert
-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Chuck Karish Sent: 27 January 2000 16:08 To: perforce-user at perforce.com Subject: RE: [p4] Restrict use of p4 user command
That would restrict access to the depot but would not restrict the ability to create users. The administrator would have to use the "allusers" list to determine which users were valid, and remove the others by hand or by script.
At 07:54 AM 1/27/00 , Robert Cowham wrote:
Recommended way of doing this is to create a group e.g.
p4 group allusers
and add all existing users to the group.
Then use p4 protect and remove any permissions to "*" in users column, instead use your new groupname.
Robert
-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Steve Cook Sent: 27 January 2000 15:28 To: 'perforce-user at perforce.com' Subject: [p4] Restrict use of p4 user command
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