-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
9
-
- We have a BUG ticket opened as the JVM argument -Dupm.pac.disable=true is not working to disable the UPM connectivity as per BUG ticket https://jira.atlassian.com/browse/JSWSERVER-19792
- In the scenario when a Customer uses Proxy, and the server does not have outgoing traffic opened, and accidently enable / checks the Connect to the Atlassian Marketplace option in the Manage Apps > Settings, this page will not be accessible and the Customer will receive a HTTP 504 timeout from the proxy. As the server does not have connectivity to outside world ( outgoing traffic blocked ), the Proxy is not able to complete the request and times out.
- The only currently way in this scenario to resolve this is bypassing the proxy so it can be disabled back from Jira UI. Bypassing the proxy is not alwasy a feasible solution for the Customers, as it may require down-time, if there is no other HTTP connector configured.
This Feature Request suggest to implement a Jira REST API Endpoint to disable UPM connectivity, so the Manage Apps page can be accessed via Proxy afterwards, when this incident in this scenario occurs.
[JSWSERVER-25936] Provide a Jira REST API Endpoint to disable UPM connectivity
Support reference count | New: 9 |
UIS | Original: 1 | New: 2 |
UIS | Original: 2 | New: 1 |
UIS | Original: 0 | New: 2 |
UIS | Original: 1 | New: 0 |
UIS | Original: 0 | New: 1 |
UIS | Original: 1 | New: 0 |
UIS | New: 1 |
Description |
Original:
* We have a BUG ticket opened as the JVM argument *{{-Dupm.pac.disable=true}}* is not working to *disable* the UPM connectivity as per BUG ticket https://jira.atlassian.com/browse/JSWSERVER-19792
* In the scenario when a Customer uses Proxy, and the server does not have outgoing traffic opened, and accidently *enable* / *checks* the _*Connect to the Atlassian Marketplace*_ option in the *Manage Apps* > {*}Settings{*}, this page will not be accessible and the Customer will receive a HTTP 504 timeout from the proxy. As the server does not have connectivity to outside world ( outgoing traffic blocked ), the Proxy is not able to complete the request and times out. * The only currently way in this scenario to resolve this is *bypassing* *the proxy* so it can be disabled back from Jira UI. Bypassing the proxy is not alwasy a feasible solution for the Customers, as it may require down-time, if there is no other HTTP connector configured. This Feature Request suggest to implement a Jira REST API Endpoint to disable UPM connectivity, so the *Manage Apps* page can be accessed via Proxy afterwards, when this incident occurs. |
New:
* We have a BUG ticket opened as the JVM argument *{{-Dupm.pac.disable=true}}* is not working to *disable* the UPM connectivity as per BUG ticket https://jira.atlassian.com/browse/JSWSERVER-19792
* In the scenario when a Customer uses Proxy, and the server does not have outgoing traffic opened, and accidently *enable* / *checks* the _*Connect to the Atlassian Marketplace*_ option in the *Manage Apps* > {*}Settings{*}, this page will not be accessible and the Customer will receive a HTTP 504 timeout from the proxy. As the server does not have connectivity to outside world ( outgoing traffic blocked ), the Proxy is not able to complete the request and times out. * The only currently way in this scenario to resolve this is *bypassing* *the proxy* so it can be disabled back from Jira UI. Bypassing the proxy is not alwasy a feasible solution for the Customers, as it may require down-time, if there is no other HTTP connector configured. This Feature Request suggest to implement a Jira REST API Endpoint to disable UPM connectivity, so the *Manage Apps* page can be accessed via Proxy afterwards, when this incident in this scenario occurs. |
Description |
Original:
* We have a BUG ticket opened as the JVM argument *{{-Dupm.pac.disable=true}}* is not working to *disable* the UPM connectivity as per BUG ticket https://jira.atlassian.com/browse/JSWSERVER-19792
* In case the Customer uses Proxy and checks the _*Connect to the Atlassian Marketplace*_ option in the *Manage Apps* > {*}Settings{*}, this page will not be accessible and the Customer will receive a HTTP 504 timeout from the proxy. * The only currently way to resolve this is *bypassing* *the proxy* so it can be disabled from Jira UI. Bypassing the proxy is not alwasy a feasible solution for the Customers, as it may require down-time, if there is no other HTTP connector configured. This Feature Request suggest to implement a Jira REST API Endpoint to disable UPM connectivity, so the *Manage Apps* page can be accessed via Proxy afterwards, when this incident occurs. |
New:
* We have a BUG ticket opened as the JVM argument *{{-Dupm.pac.disable=true}}* is not working to *disable* the UPM connectivity as per BUG ticket https://jira.atlassian.com/browse/JSWSERVER-19792
* In the scenario when a Customer uses Proxy, and the server does not have outgoing traffic opened, and accidently *enable* / *checks* the _*Connect to the Atlassian Marketplace*_ option in the *Manage Apps* > {*}Settings{*}, this page will not be accessible and the Customer will receive a HTTP 504 timeout from the proxy. As the server does not have connectivity to outside world ( outgoing traffic blocked ), the Proxy is not able to complete the request and times out. * The only currently way in this scenario to resolve this is *bypassing* *the proxy* so it can be disabled back from Jira UI. Bypassing the proxy is not alwasy a feasible solution for the Customers, as it may require down-time, if there is no other HTTP connector configured. This Feature Request suggest to implement a Jira REST API Endpoint to disable UPM connectivity, so the *Manage Apps* page can be accessed via Proxy afterwards, when this incident occurs. |