Zero Downtime Upgrades and Apps

Hi,

a customer reported an issue with Zero Downtime Upgrades.

Our app is not working/accessible anymore after performing the upgrade unless they log in locally first. Afterwards, it works fine. Trying to go to a URL of the app results in a 503, and the same goes for trying to do a rest call. There are no log messages either.

Is that intended behavior?
It looks like Atlassian locks down the instance unless someone logs in locally first. The consequence is that no one can log in via our SSO app unless someone logs in locally first. Additionally (even if we do not recommend this), there are customers with no local login, thus they would get locked out of their instance in worst case.

Best regards,
Christopher

4 Likes

Hi,
I am the customer :slight_smile:
The same happened yesterday after updating Jira Core to 9.12.6.
After the Update I’d to have login via local.
If this is intended behavior it is obstructive. Has anyone taking notice of that?