-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.2.1
-
None
-
6.02
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Problem
After fully restoring a fresh OnDemand backup into a fresh JIRA 6.2.1 instance, no user is able to log into the application.
Expected results
JIRA should allow all users to successfully log into the application
Actual Results
All users (including sysadmin) get a "You do not have a permission to log in. If you think this is incorrect, please contact your JIRA administrators." error message.
atlassian-jira.security.log displays the following
2014-03-20 13:46:56,834 http-bio-8080-exec-1 anonymous 826x106x1 1p3qqqo 127.0.0.1 /rest/gadget/1.0/login The user 'sysadmin' is NOT AUTHORIZED to perform to login for this request 2014-03-20 13:46:56,834 http-bio-8080-exec-1 anonymous 826x106x1 1p3qqqo 127.0.0.1 /rest/gadget/1.0/login login : 'sysadmin' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.
No error is logged into catalina.out (or atlassian.jira.log).
Everything seems correct in the database side (cwd_user/app_user/cwd_membership/cwd_directory tables)
Workaround
- Import OnDemand backup using JIRA 6.2
- Shutdown the instance
- Start JIRA 6.2.1 pointing to the JIRA 6.2 database
JIRA will upgrade the 6.2 database and you can use your JIRA 6.2.1 successfully
- relates to
-
-
- Closed
-
[JRASERVER-37574] Unable to log in after JIRA OnDemand restore into JIRA Standalone
Hi All
Thanks for the info.
Unfortunately, in my environment it is not that straightforward. The server is production, therefore I do not have direct access to it to simply add new Jira versions etc etc. I now have to go to the prod sysadms, get them to install the old version etc etc.
Sigh.
But thanks again for the assistance.
Michael
Michael,
I am in the same boat as you.
The workaround is –
Import OnDemand backup using JIRA 6.2
Shutdown the instance
Start JIRA 6.2.1 pointing to the JIRA 6.2 database
JIRA will upgrade the 6.2 database and you can use your JIRA 6.2.1 successfully Activity
Unfortunately my ondemand build# ( 6253) is higher than JIRA 6.2 ( 6252) so I am unable to import the backup. ( https://answers.atlassian.com/questions/272541/migrating-jira-from-ondemand-6-2-6253-to-local-6-2-6252)
Hi;
Just install version 6.2, not 6.2.1. Import backup to 6.2
Documentation on https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+OnDemand+to+a+JIRA+Installed+Site explains the procedure. This workaround fixed our problem.
Regards
Hi
I have just encountered this problem today while testing our in-house production servers. We had scheduled to bring Jira & Confluence in-house this week-end and have now had to delay.
I have checked the Migration Guide above and can find no reference to any temporary workaround instructions. Can you point me to their location?
Also, I see that this issue is unassigned. What estimates do you have for a resolution?
Regards
Michael
The documentation has been updated to provide temporary workaround instructions: https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+OnDemand+to+a+JIRA+Installed+Site
I'm still getting this using a backup of OD 6.3 taken 4th June.
It MUST be loaded into JIRA 6.2.6 because the importer won't let you otherwise.
I still now can't login because I can't load the backup into 6.2 and then upgrade to 6.2.6
Please advise?