Suggestion - Undo checkout should be a security option

danialgibson · Post by **danialgibson** » Wed Aug 10, 2005 5:11 pm

We use Vault to store stuff from multiple departments - the help desk people use it for various things and the programmers use it for other things. Generally a programmer should not be able to see help desk projects - this is fine, standard vault security works well.

If someones computer dies or gets renamed or whatever and they need to undo a checkout, they can't. The admin must do it. We'd like it so that the programmers (or maybe just the lead programmers) and undo a checkout in the repository that they are allowed access to. We don't want to have to give everyone the admin password.

So it would be nice if the undo checkout feature was a security option, just like checkout/checkin is.

lbauer · Post by **lbauer** » Thu Aug 11, 2005 8:18 pm

I'll add this as a feature request.

lbauer · Post by **lbauer** » Mon Aug 15, 2005 12:23 pm

I could use some clarification -- do you want users to be able to undo their own checkouts from a different machine? This is already possible in Vault 3.x.

Or do you want non-Admins to be able to undo checkouts of other users?

danialgibson · Post by **danialgibson** » Mon Aug 15, 2005 4:29 pm

Non-admins to be able to undo checkouts of other users in a certain repository (not all repositories).

danialgibson · Post by **danialgibson** » Thu Aug 18, 2005 5:20 pm

We just moved to active directory and before the move I had some files checked out. After the move to AD my checked out files no longer show in the bottom panel where they normally show. I can undo the checkout by going into the folder and selecting each file, but I can't see them down the bottom as I normally can. So when I first logged on, it was like the files were not checked out to me, even though they actually were.

The machine is actually a VMWare machine. Before the move I was logging on to windows as user X. After the move to AD I log on as Administrator. Maybe the search down the bottom is based on machinename, windowsUsername, vaultUsername? If so, why use the windows user name? Shouldn't it just be machinename, vaultUsername?

lbauer · Post by **lbauer** » Fri Aug 19, 2005 10:50 am

Client side cache files are stored in the logged-in user's appdata or userprofile directory. So if you log in to Windows as UserA and then log in as UserB, the Pending change set, etc. will be different.

Details here:
http://support.sourcegear.com/viewtopic.php?t=6