I am working on a project to create an electronic document with FDA documents that is compatible with the FDA. The mandate is that it uses Perforce to track various document changes, use LDAP (AD) as the authentication / access directory, and re-authenticate the user when the change list is submitted.
The first two requirements exist, but I have problems with the latter. I have a script in the "change-submit" trigger that logs the user out of the user account - assuming that this forces the client to re-authenticate the user before continuing with the process, but this will not work, at least for the linear client command; the user logs out, but the process ends, and the next attempt to command from the user is the one that receives the denial.
Setting up a script to handle the authentication process is not an option, as it runs on the server side, and there is no way to pass the request to the user.
I could, of course, pass authentication as command-line arguments to the script, and then return non-0 to cause the process to abort if the credentials are false, but I did not find a way to change the commands sent for this action using the p4v GUI , and again, so that the client requests authentication from the user; and this will result in the password being displayed as clear text in sequence.
Setting a timeout on a ticket to an extremely short duration will definitely require authentication by the user before sending, but also before any other actions.
Has anyone done something there before, or does anyone see an angle of attack that I miss? Thanks!
Mike
source
share