-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
Jenkins ver. 2.86, Windows, P4 1.8.5
I'm trying to add a Perforce Password Credential to connect to a remote replica server but I'm having issues connecting. I'm using an SSL connection and have confirmed the credentials work and triple checked I am using the correct fingerprint.
When I hit "Test Connection" it spins for a short while then spits out "Server Connection Error.".
From looking at the system logs I see this error which seems to indicate it is trying to connect with the username "nouser" though this is not the username that I have entered.
Jun 20, 2018 5:14:35 AM SEVERE org.jenkinsci.plugins.p4.client.ConnectionHelper connect P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Access for user 'nouser' has not been enabled by 'p4 protect'. Jun 20, 2018 5:14:35 AM INFO org.jenkinsci.plugins.p4.client.ConnectionHelper P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Access for user 'nouser' has not been enabled by 'p4 protect'. Jun 20, 2018 5:14:35 AM SEVERE org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry P4: Connection retry: 1 Jun 20, 2018 5:14:35 AM INFO org.jenkinsci.plugins.p4.client.ConnectionHelper P4: Connection retry: 1 Jun 20, 2018 5:14:38 AM SEVERE org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry P4: Connection retry giving up... Jun 20, 2018 5:14:38 AM INFO org.jenkinsci.plugins.p4.client.ConnectionHelper P4: Connection retry giving up...
Any idea why this would happen? Connections to our own Perforce servers are connecting fine.
[JENKINS-52060] Credentials issue: Access for user 'nouser' has not been enabled by 'p4 protect'.
Karl Wirth
added a comment - Hi alexgeek did you solve this problem or did you just avoid using the remote server?
Karl Wirth
added a comment - Hi alexgeek did you solve this problem or did you just avoid using the remote server? Karl Wirth
added a comment - Closing for now. Happy to reopen if this becomes an issue again. 
Emanuel May
added a comment - We actually have the same issue right now. We have to connect to a remote server we have no control over and can only connect via SSL. Same problem happens as described above: Login is tried with the username "nouser", despite us setting up the correct username. Was there any work done in this regard or any work-arounds we can use?
Emanuel May
added a comment - We actually have the same issue right now. We have to connect to a remote server we have no control over and can only connect via SSL. Same problem happens as described above: Login is tried with the username "nouser", despite us setting up the correct username. Was there any work done in this regard or any work-arounds we can use? Karl Wirth
added a comment - Hi emanuel_may - Is this still happening? Does it work when you point the Jenkins system and try the same test? Also which version of P4Jenkins are you using?
Also please log into the OS and see if P4CHARSET is set somewhere in the environment. For example:
- echo $P4CHARSET
- echo %P4CHARSET%
- p4 set
- Look in any Config file that matches the name setup for P4CONFIG when you run 'p4 set'.
Thanks,
Karl
Karl Wirth
added a comment - Hi emanuel_may - Is this still happening? Does it work when you point the Jenkins system and try the same test? Also which version of P4Jenkins are you using?
Also please log into the OS and see if P4CHARSET is set somewhere in the environment. For example:
echo $P4CHARSET
echo %P4CHARSET%
p4 set
Look in any Config file that matches the name setup for P4CONFIG when you run 'p4 set'.
Thanks,
Karl
Emanuel May
added a comment - Hey p4karl,
It is still happening. I'm not sure what you mean when you say "point the Jenkins system", sorry.
We are using the latest P4 Plugin for Jenkins. Should be 1.10.14.
P4CHARSET does not seem to be set on the machines we run the commands on. This is a snippet from powershell outside of Jenkins:
And this is from a powershell command from within a Jenkins job:
We also don't use any P4CONFIG files and the system is pretty much a fresh installation (just two weeks ago).
Any help is greatly appreciated!
Emanuel May
added a comment - Hey p4karl ,
It is still happening. I'm not sure what you mean when you say "point the Jenkins system", sorry.
We are using the latest P4 Plugin for Jenkins. Should be 1.10.14.
P4CHARSET does not seem to be set on the machines we run the commands on. This is a snippet from powershell outside of Jenkins:
And this is from a powershell command from within a Jenkins job:
We also don't use any P4CONFIG files and the system is pretty much a fresh installation (just two weeks ago).
Any help is greatly appreciated! Emanuel May
added a comment - Any news on this? Anything we can provide that can help troubleshoot the issue?
Emanuel May
added a comment - Any news on this? Anything we can provide that can help troubleshoot the issue? Karl Wirth
added a comment - Hi emanuel_may - I apologise I missed your update last week. I'm not sure what I meant when I said "point the jenkins system". Maybe that was why I didnt finish the sentence sorry.
Can you please send an email to 'support@perforce.com' with the output from 'p4 info' run against your Perforce server. I'd like to have a Zoom meeting with you this week to see what's happening.
Karl Wirth
added a comment - Hi emanuel_may - I apologise I missed your update last week. I'm not sure what I meant when I said "point the jenkins system". Maybe that was why I didnt finish the sentence sorry.
Can you please send an email to 'support@perforce.com' with the output from 'p4 info' run against your Perforce server. I'd like to have a Zoom meeting with you this week to see what's happening.
Karl Wirth
added a comment - We have found out that ther server causing the following error when trying to create a credential:
Access for user 'nouser' has not been enabled by 'p4 protect'
activly hangs 'p4 info' if you are not logged in. This is not standard Perforce behavior but is an added security feature at this site. This will block any commands run by P4Java (which always runs 'p4 info') causing the error above.
Karl Wirth
added a comment - We have found out that ther server causing the following error when trying to create a credential:
Access for user 'nouser' has not been enabled by 'p4 protect'
activly hangs 'p4 info' if you are not logged in. This is not standard Perforce behavior but is an added security feature at this site. This will block any commands run by P4Java (which always runs 'p4 info') causing the error above. 
From some digging a colleague did, part of the issue seems to be caused by our Jenkins master and the nodes having P4CHARSET set to utf8 but this external server is not using utf8.