Hide Forgot
Description of problem: The redhat-access-gui tool does not accept http_proxy or https_proxy, I want to know how to set proxy for redhat-access-gui tool. Version-Release number of selected component (if applicable): redhat-access-gui-1.0.0-6.el7.noarch.rpm How reproducible: In an internal network, try to use redhat-access-gui with proxy setting, but failed. The proxy is correct because I can login to access.redhat.com using firefox. Steps to Reproduce: 1.Install redhat-access-gui 2.Set http_proxy and https_proxy on bash cmd line export http_proxy=XX.XX.XX.XX:3128 export https_proxy=XX.XX.XX.XX:3128 3.Run redhat-access-gui 4.Try to login with RHN login id. Actual results: Login failed, from the tcpdump, the communication to https://api.access.redhat.com does not go through proxy server Expected results: Login success the communication to https://api.access.redhat.com go through proxy server Additional info: Maybe redhat-access-gui does not have this feature, then it would be a new feature request.
Created attachment 1208309 [details] modified redhat_access.py based on redhat-access-gui-1.0.0-6
Created attachment 1208310 [details] modified redhat_access.ui based on redhat-access-gui-1.0.0-6
Hello, Proxy support should be easy to implement, as redhat_support_lib API already provide these options. /usr/lib/python2.7/site-packages/redhat_support_lib/api.py ~~~ class API(object): def __init__(self, username, password, url='https://api.access.redhat.com', key_file=None, cert_file=None, proxy_url=None, proxy_user=None, proxy_pass=None, ftp_host='dropbox.redhat.com', ftp_port=21, ftp_user=None, ftp_pass=None, ftp_dir="/incoming", timeout=None, userAgent=None, no_verify_ssl=False, ssl_ca=None): ~~~ A modified version of `redhat-access-gui` is attached as attachment 1208309 [details] & 1208310. Apologize that I didn't make it a patch file as I couldn't find the git tree. feichashao
Created attachment 1208311 [details] Added proxy support. This patch is based on redhat-access-gui-1.0.0-6
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.