Bug 2003530

Summary: [RFE]Creating a new HTTP Proxy in satellite GUI should have an option to automatically update/set the "Default HTTP Proxy setting", in the "Administer menu" .
Product: Red Hat Satellite Reporter: Satyajit Das <sadas>
Component: NetworkingAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.0CC: ahumbe, dhjoshi, lstejska, saydas, thadzhie
Target Milestone: UnspecifiedKeywords: FutureFeature, PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Satyajit Das 2021-09-13 07:01:33 UTC 
1. Proposed title of this feature request

Creating a new HTTP Proxy in satellite GUI should have an option to automatically update/set the "Default HTTP Proxy setting", no need to navigate to "Administer menu" to update/set global default proxy again.

2. What is the nature and description of the request?

Many organizations utilizing Red Hat Satellite have network policies that block direct access to the internet by the Satellite Server, 
and instead require that the Satellite Server go through an HTTP proxy to access the internet to synchronize content. 

Currently, to configuring a Global Proxy in Satellite, we have to follow the below steps:-

Satellite WebUI > Infrastructure menu and select HTTP Proxies // Define the proxy details.

Then, he has to  configure Satellite to use this newly created proxy as the global default proxy.  // Most of the customer missed this step 

Steps:-
======
Administer menu, and select Setting >  Content tab > Default HTTP Proxy setting > Select the one he created earlier.


3. Why does the customer need this? (List the business requirements here)

In one page the customer can define/update/set the "Default HTTP Proxy setting", since Satellite doesn’t have an HTTP proxy setting at the organization level, 
and the Default HTTP Proxy setting is global to all organizations. so manaully again going to Administer menu, and update the "Default HTTP Proxy setting" does not make much sense.

4. How would the customer like to achieve this? (List the functional requirements here)

I am suggesting to put an option in the HTTP Proxies page to update/set the "Default HTTP Proxy setting". 
so that customers don't have to navigate to the "Administer menu, and select Setting >  Content tab > Default HTTP Proxy setting > content" to update the settings.


5. Is there already an existing RFE upstream or in Red Hat Bugzilla?

Unknown

6. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No

7. Is the sales team involved in this request and do they have any additional input?
No


8. List any affected packages or components.
Unknown
Comment 1 Sayan Das 2021-09-13 09:07:46 UTC 
I will add my point of view here as well which I had mentioned to the reporter of this bug.

1. If someone is creating a proxy they should have an option to set it as the content_default_http_proxy on the same form by use of a checkbox.

2. If someone has created two proxies and has set the first one as content_default_http_proxy , then if he tries to do the same for the second proxy, then a warning should appear saying "<Proxy_Name> is already set as the content_default_http_proxy. Do you want to overwrite this change ?" and Yes\No options should appear.

3. If someone wants to delete a http_proxy and that is set as content_default_http_proxy, delete action should unset the value of content_default_http_proxy as well.