Need for proxy bypass for deploying MCAS log collector

%3CLINGO-SUB%20id%3D%22lingo-sub-1978615%22%20slang%3D%22en-US%22%3ENeed%20for%20proxy%20bypass%20for%20deploying%20MCAS%20log%20collector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1978615%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3EI%20have%202%20doubts%20regarding%20MCAS%20log%20collector%20deployment%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EWhile%20going%20through%20Microsoft%20documentation%20I%20found%20that%20we%20have%20to%20bypass%20proxy%20authentication%20for%20deploying%20log%20collector.%20What%20happens%20if%20we%20don't%20bypass%20the%20proxy%20authentication%3F%3C%2FLI%3E%3CLI%3EBelow%20is%20a%20sample%20image%20of%20log%20collector%20from%20Microsoft%20documentation%26nbsp%3B(echo%206f19225ea69cf5f178139551986d3d797c92a5a43bef46469fcc997aec2ccc6f)%20%7C%20docker%20run%20--name%20MyLogCollector%20-p%2021%3A21%20-p%2020000-20099%3A20000-20099%20-e%20%22PUBLICIP%3D'192.2.2.2'%22%20-e%20%22%3CSTRONG%3EPROXY%3D192.168.10.1%3A8080%3C%2FSTRONG%3E%22%20-e%20%22CONSOLE%3Dtenant2.eu1-rs.adallom.com%22%20-e%20%22COLLECTOR%3DMyLogCollector%22%20--security-opt%20apparmor%3Aunconfined%20--cap-add%3DSYS_ADMIN%20--restart%20unless-stopped%20-a%20stdin%20-i%20mcr.microsoft.com%2Fmcas%2Flogcollector%20starter%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BSo%20in%20the%20field%20bolded%20%22%26nbsp%3B%3CSTRONG%3EPROXY%3D192.168.10.1%3A8080%22%20%2C%26nbsp%3B%3C%2FSTRONG%3E%20what%20does%20providing%20the%20proxy%20ip%20and%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3Bport%20do%20in%20this%20case%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20provide%20answers%20asap..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1978615%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20App%20Security%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECloud%20Discovery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2003017%22%20slang%3D%22en-US%22%3ERe%3A%20Need%20for%20proxy%20bypass%20for%20deploying%20MCAS%20log%20collector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2003017%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F694219%22%20target%3D%22_blank%22%3E%40Rhul1545%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPROXY%3D192.168.10.1%3A8080%26nbsp%3B%3C%2FSTRONG%3E-%20If%20you%20have%20a%20Proxy%20deployed%20in%20your%20environment%2C%20this%20is%20how%20you%20would%20configure%20the%20Log%20Collector%20to%20send%20traffic%20to%20it.%20The%20IP%20is%20the%20IP%20of%20your%20Proxy%20and%20the%20port%20is%20the%20port%20your%20Proxy%20appliance%20needs%20to%20be%20listening%20on%20for%20traffic%20from%20the%20Log%20Collector.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20not%20sure%20about%20bypassing%20authentication.%20I%20haven't%20heard%20of%20that%20and%20can't%20find%20it%20in%20documentation.%20Would%20you%20mind%20linking%20the%20article%20you%20saw%20this%20at%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All,

I have 2 doubts regarding MCAS log collector deployment

 

  1. While going through Microsoft documentation I found that we have to bypass proxy authentication for deploying log collector. What happens if we don't bypass the proxy authentication?
  2. Below is a sample image of log collector from Microsoft documentation (echo 6f19225ea69cf5f178139551986d3d797c92a5a43bef46469fcc997aec2ccc6f) | docker run --name MyLogCollector -p 21:21 -p 20000-20099:20000-20099 -e "PUBLICIP='192.2.2.2'" -e "PROXY=192.168.10.1:8080" -e "CONSOLE=tenant2.eu1-rs.adallom.com" -e "COLLECTOR=MyLogCollector" --security-opt apparmor:unconfined --cap-add=SYS_ADMIN --restart unless-stopped -a stdin -i mcr.microsoft.com/mcas/logcollector starter

         So in the field bolded " PROXY=192.168.10.1:8080" ,  what does providing the proxy ip and               port do in this case?

 

Please provide answers asap..

 

Thanks 

1 Reply

@Rhul1545 

PROXY=192.168.10.1:8080 - If you have a Proxy deployed in your environment, this is how you would configure the Log Collector to send traffic to it. The IP is the IP of your Proxy and the port is the port your Proxy appliance needs to be listening on for traffic from the Log Collector. 

 

I'm not sure about bypassing authentication. I haven't heard of that and can't find it in documentation. Would you mind linking the article you saw this at?