Application is not web proxy aware, not functional inside corporate networks

[noovolari]

Application is not web proxy aware, not functional inside corporate networks

[andreacavagna01]

Hi @ashishdesaifmr, thanks for the issue report, we are working on a solution that will implement your needs.
Is in the refactoring point of our Roadmap.

I have a question for you, which Cloud Providers are you using in your company?

[ashishdesaifmr]

We current use aws and azure

…

________________________________ From: Andrea Cavagna <[email protected]> Sent: Saturday, August 29, 2020 10:05:39 AM To: Noovolari/leapp <[email protected]> Cc: Desai, Ashish <[email protected]>; Mention <[email protected]> Subject: Re: [Noovolari/leapp] Application is not web proxy aware, not functional inside corporate networks (#8) This email is from an external source - exercise caution regarding links and attachments. Hi @ashishdesaifmr<https://github.com/ashishdesaifmr>, thanks for the issue report, we are working on a solution that will implement your needs. Is in the refactoring point of our Roadmap<https://github.com/Noovolari/leapp/projects/1>. I have a question for you, which Cloud Providers are you using in your company? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#8 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMT4JDXR5J4W7BUQIYWPE6TSDEDLHANCNFSM4QOE33YQ>.

[andreacavagna01]

Hi @ashishdesaifmr, Today we are releasing the support to Azure as Cloud Provider, than The proxy feature is the next :)

[ericvilla]

Hi @ashishdesaifmr, we're working on the HTTP Proxy Configuration support. We've already implemented the in-app HTTP Proxy Pass, i.e. make HTTP calls issued by Leapp pass through the Proxy specified in the HTTP Proxy Configuration. Moreover, we are on the way to add support for Proxy authentication, adding username and password to the HTTP Proxy Configuration.

I've just a question for you: what's your opinion about the possibility to make Leapp inherit Proxy OS Configuration? We're trying to understand if it is a critical feature that we should ship with the release v0.3.0, and external feedback would be useful.

Thank you!

[ashishdesaifmr]

Hi Eric, Inheriting the OS level configs is not important. In fact at times we really like the ability to override the OS level proxy configs as corporate environments have complex configs and at time we need to route via a specific proxy vs using what the OS level config has. Hope this helps, Ashish From: Eric Villa <[email protected]> Sent: Thursday, October 8, 2020 4:11 AM To: Noovolari/leapp <[email protected]> Cc: Desai, Ashish <[email protected]>; Mention <[email protected]> Subject: Re: [Noovolari/leapp] Application is not web proxy aware, not functional inside corporate networks (#8) This email is from an external source - exercise caution regarding links and attachments. Hi @ashishdesaifmr<https://github.com/ashishdesaifmr>, we're working on the HTTP Proxy Configuration support. We've already implemented the in-app HTTP Proxy Pass, i.e. make HTTP calls issued by Leapp pass through the Proxy specified in the HTTP Proxy Configuration. Moreover, we are on the way to add support for Proxy authentication, adding username and password to the HTTP Proxy Configuration. I've just a question for you: what's your opinion about the possibility to make Leapp inherit Proxy OS Configuration? We're trying to understand if it is a critical feature that we should ship with the release v0.3.0, and external feedback would be useful. Thank you! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#8 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMT4JDRCATWMEFOMQVOARTLSJVXYFANCNFSM4QOE33YQ>.

[pethron]

I think that right now we can settle with the custom proxy as it only needs to be configured to work for everyone.
We can add at a later time the inheritance from OS configuration.

[ericvilla]

Hi @ashishdesaifmr,

thank you for your feedback! I agree with @pethron; we can rely on in-app proxy configuration and focus on os's proxy configuration at a later time.

Just to be clear, I will highlight the fact that we're covering only HTTP/HTTPS requests made by Leapp, i.e. logins and logouts against G Suite. Those are the only HTTP/HTTPS requests made by the client.

I will give you updates regarding the Proxy Authentication feature development.

Thank you!

[urz9999]

added in 0.3.0. Please check the option page for configuration parameters.