Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
Hi,
I have started to get an error with perforce about the password being invalid or unset with repositories that were working previously. It looks like they are failing when they try to update the client spec workspace with the command: p4 -p server:portnumber -u perforceuser -P ****** -c clientspec client -i
Our off site perforce administrator says that this happening because of the security level on perforce server is on level 3 which doesn't allow password based authentication and only allows ticket based authentication so using -P won't work.
Would there be a way to force Quick Build to use ticket authentication? We are somewhat blocked by this as our security level will not be lowered since it's mandatory by company policy.
-
replies
3
-
views
3691
-
stars
0
-
QB always uses ticket to login to perforce, here the param passed to "-P" is actually content of the ticket fetched via command "p4 -u perforceuser -p". Can you please run this command on the machine, and pass the returned ticket content to execute any p4 command to see if it works?, for instance:
p4 -p server:portnumber -u perforceuser -P <ticket content> -c clientspec client -o
I will try when i get in the office tomorrow morning (GMT -4). If the command succeeds or does not what would be the next steps?
I think i've narrowed the issue down. We have perforce proxy which points to and perforce edge server. This edge server connects to another server which is the commit server. Therefore when the command
p4 -p perforceserverproxy:portnumber -u perforceuser login -p executes it produce two tickets one after the other which are different. I believe that QB is attempting to use the ticket from commit server as that is the last ticket gets generated but this will not work since the workspace is local by default and not present on the commit-server.
Is there a way around this?
Update: We've managed to get working again by invalidating all tickets for the user on the machine using p4 -p perforceserverproxy:portnumber logout -a. Now the right ticket is being used by QB
