-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
Issue Summary
When you have more than one authentication method set up in Jira, enables ZDU and start upgrading your nodes, if there's a dismissible warning then you won't be able to ignore the errors and continue.
The UI will break with the following error when you hit "Ignore all warnings and continue"
This happens because the new authentication methods provided by the plugin version 4.2 retrieves the available directories through the endpoint /rest/authconfig/1.0/login-options, however, this endpoint is not whitelisted on Johnson's filter whitelist so a 503 is received by the plugin when trying to retrieve it:
Steps to Reproduce
- Set up more than one authentication method in Authentication Methods (available as of 4.12)
- Put the cluster in upgrade mode and upgrade a single node.
- The node should either have some sort of configuration problem that would prompt a warning Johnson Page;
- Click the "Ignore all warnings and continue" button
Expected Results
The admin is able to dismiss the warnings page and log in on the node.
Actual Results
The user is unable to log in, so the error message cannot be dismissed from the UI.
Workaround
The workaround is to fix the warnings.
Notes
Starting in Jira 8.16, we have upgraded the Postgres driver version. This new version enforces the socketTimeout parameter (JRASERVER-71982) and will bring Johnson's warning page if the user doesn't add them, thus increasing the likelihood of users facing this problem.
- is related to
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
- is cloned by
-
AAUTH-576 Failed to load
[SAMLDC-89] 4.2.x breaks ZDU when there's a Johnson dismissible warning
| Workflow | Original: SAMLDC Workflow v2 [ 4130722 ] | New: JAC Bug Workflow v3 [ 4271549 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Done [ 10044 ] |
| Fix Version/s | New: 4.2.5 [ 97705 ] | |
| Fix Version/s | New: 4.1.9 [ 97704 ] | |
| Fix Version/s | New: 4.0.11 [ 97703 ] | |
| Fix Version/s | New: 3.2.7 [ 97702 ] |
| Assignee | New: Patryk [ ppetrowski ] |
| Remote Link | New: This issue links to "AAUTH-576 (Current JIRA)" [ 560604 ] |
| Labels | New: short-term-backlog |
| Description |
Original:
h3. Issue Summary
When you have more than one authentication method set up in Jira, enables ZDU and start upgrading your nodes, if there's a dismissible warning then you won't be able to ignore the errors and continue. The UI will break with the following error when you hit "Ignore all warnings and continue" !image-2021-06-07-21-03-28-239.png|thumbnail! This happens because the new authentication methods provided by the plugin version 4.2 retrieves the available directories through the endpoint {{/rest/authconfig/1.0/login-options}}, however, this endpoint is not whitelisted on Johnson's filter whitelist: !Screen Shot 2021-06-07 at 9.08.09 PM.png|thumbnail! h3. Steps to Reproduce # Set up more than one authentication method in *Authentication Methods* (available as of 4.12) # Put the cluster in upgrade mode and upgrade a single node. # The node should either have some sort of configuration problem that would prompt a warning Johnson Page; # Click the "Ignore all warnings and continue" button h3. Expected Results The admin is able to dismiss the warnings page and log in on the node. h3. Actual Results The user is unable to log in, so the error message cannot be dismissed from the UI. h3. Workaround The workaround is to fix the warnings. h3. Notes Starting in Jira 8.16, we have upgraded the Postgres driver version. This new version enforces the {{socketTimeout}} parameter ( |
New:
h3. Issue Summary
When you have more than one authentication method set up in Jira, enables ZDU and start upgrading your nodes, if there's a dismissible warning then you won't be able to ignore the errors and continue. The UI will break with the following error when you hit "Ignore all warnings and continue" !image-2021-06-07-21-03-28-239.png|thumbnail! This happens because the new authentication methods provided by the plugin version 4.2 retrieves the available directories through the endpoint {{/rest/authconfig/1.0/login-options}}, however, this endpoint is not whitelisted on Johnson's filter whitelist so a 503 is received by the plugin when trying to retrieve it: !Screen Shot 2021-06-07 at 9.08.09 PM.png|thumbnail! h3. Steps to Reproduce # Set up more than one authentication method in *Authentication Methods* (available as of 4.12) # Put the cluster in upgrade mode and upgrade a single node. # The node should either have some sort of configuration problem that would prompt a warning Johnson Page; # Click the "Ignore all warnings and continue" button h3. Expected Results The admin is able to dismiss the warnings page and log in on the node. h3. Actual Results The user is unable to log in, so the error message cannot be dismissed from the UI. h3. Workaround The workaround is to fix the warnings. h3. Notes Starting in Jira 8.16, we have upgraded the Postgres driver version. This new version enforces the {{socketTimeout}} parameter ( |
| Link | New: This issue is related to JRASERVER-71844 [ JRASERVER-71844 ] |