It is usually caused by plugin cache.
Please perform the following to see if the issue is fixed:
1. Shutdown JIRA
2. Delete the following hidden plugin cache directories:
3. Restart JIRA (These directories will be recreated on JIRA reboot with new plugin cache)
sorry for the inconvenience with that. There sneaked a little bug into the plugin. In result the forwarding mechanism after entering the pin successfully, results in the 404 error message. This happens especially on instances without the JIRA or confluence context in the URL.
A fix for that is already developed and currently be tested. So I am confident, we will provide a bugfix release in the next days.
we are facing a similar problem. After successfully entering a pin we get redirected back on the same page to re-enter the pin with target the Logout page, which doesn't make sense.
Any chance fro a fix?
We released Version 1.2.1 of Secure Loin for JIRA on Tuesday. It should solve the problem with the 404 messages after entering the PIN. It had been a problem with the URL forwarding in certain circumstances. But now the plugin uses relative URLS for the forwarding, and in all reproducable situations this version fixed the problem.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot