We are testing our recovery for our JIRA instance using a Postgres DB dump. Using the JIRA XML backup is not currently possible: too many fatal errors, too many rabbit holes.
The testbed JIRA also connects to a testbed version of Crowd, which is populated by the data used in the production. version The tesbed JIRA is connected to the testbed Crowd, and admin users can be verified.
Using a DB dump on a clean instance of JIRA definitely shows all the issues, but no-one can log in, not even those with admin rights. The JIRA support literature shows workarounds for finding and establishing admin users in the DB, but none of this is working.
From the logs:
2018-10-05 08:21:48,581 http-nio-8080-exec-20 ERROR anonymous 501x1227x1 1fquprk 127.0.0.1 /rest/gadget/1.0/login [c.a.j.security.login.JiraSeraphAuthenticator] Error occurred while trying to authenticate user 'XXXXXX'. com.atlassian.crowd.exception.runtime.OperationFailedException
...
Caused by: com.atlassian.crowd.exception.ApplicationPermissionException: HTTP Status 403 - Client with address "xxx.xxx.xxx.xxx" is forbidden from making requests to the application, {2}.type Status reportmessage Client with address "xxx.xxx.xxx.xxx" is forbidden from making requests to the application, {2}.description Access to the specified resource (Client with address "xxx.xxx.xxx.xxx" is forbidden from making requests to the application, {2}.) has been forbidden.Apache Tomcat/6.0.32
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.