Unable to Login to Perforce Due to 'Password Not Allowed at This Server Security Level' Error
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
This problem is related to a third party plugin, and therefore not supported by Atlassian. See Atlassian Supported Plugins for more information.
Symptoms
The JIRA Fisheye plugin is unable to login to Perforce due to error below:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<log level="VERBOSE" date="5/5/08 2:38:40 PM">From P4:error: Password not allowed at this server security level, use 'p4 login'.</log>
<log level="VERBOSE" date="5/5/08 2:38:40 PM">P4Process.readLine(): error: Password not allowed at this server security level, use 'p4 login'.</log>
<log level="VERBOSE" date="5/5/08 2:38:40 PM">From P4:exit: 1</log>
<log level="ERROR" date="5/5/08 2:38:40 PM">P4 exited with an Error!</log>
<log level="NOTIFY" date="5/5/08 2:38:40 PM">P4Process exit code: 1</log>
<log level="ERROR" date="5/5/08 2:38:40 PM">java.io.IOException: error: Password not allowed at this server security level, use 'p4 login'.
at com.perforce.api.P4Process.closeProcess(P4Process.java:587)
at com.perforce.api.Job.sync(Job.java:443)
at com.perforce.api.Job.sync(Job.java:379)
at com.perforce.api.Job.getJob(Job.java:124)
at com.atlassian.jira.plugin.ext.perforce.PerforceManagerImpl.getJob(PerforceManagerImpl.java:482)
at com.atlassian.jira.plugin.ext.perforce.issuetabpanels.job.P4JobTabPanel.getActions(P4JobTabPanel.java:45)
at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelModuleDescriptor.getActions(IssueTabPanelModuleDescriptor.java:99)
at com.atlassian.jira.web.action.issue.ViewIssue.getActions(ViewIssue.java:400)
...
Cause
The Perforce security level is set to level 3 which requires ticket based authentication.
Workaround
Create a file which stores the location of the tickets. The p4.ticketfile should be changed to p4tickets.txt. The p4tickets.txt should then reside in the classpath <install directory\atlassian-jira\WEB-INF\classes.
Resolution
Perforce integration is now handled through the JIRA Fisheye Plugin.
Was this helpful?