It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.
These forums are peer-to-peer, best effort, volunteer run and that if your issue is urgent or not getting a response, you might try one of the following options:
Sometimes this automatic posting will alert someone that can respond.
If this is a reply to a duplicate posting or otherwise posted in error, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot.
To download url based threat intelligence data sources using a proxy, please follow the below steps,
1. First, configure your proxy server 2. If you are accessing proxy over https, add below settings in /etc/opt/novell/sentinel/config/configuration.properties https.proxyHost=<proxy host/ip> https.proxyPort=<proxy port> 3. If proxy is over http, add below settings in /etc/opt/novell/sentinel/config/configuration.properties http.proxyHost=<proxy host/ip> http.proxyPort=<proxy port> 4. In configuration.properties file, set the value of http.nonProxyHosts to pipe separated host addresses for which you don’t want the connection to go through a proxy. This means that sentinel makes direct connection to these configured hosts rather using proxy. By default this should contain loopback, local sentinel ip, host info of any distributed targets configured, host info of slink server, host info of scm server as these should not go through a proxy. Host details can contain wildcard characters(*.acme.com) and multiple host info should get separated by ‘|’ http.nonProxyHosts=127.0.0.1|<sentinelip>|<disttargetipip>|<slink server>|<scm server|<advisorserver> 5. Restart sentinel
To download url based threat intelligence data sources using a proxy, please follow the below steps,
1. First, configure your proxy server 2. If you are accessing proxy over https, add below settings in /etc/opt/novell/sentinel/config/configuration.properties https.proxyHost=<proxy host/ip> https.proxyPort=<proxy port> 3. If proxy is over http, add below settings in /etc/opt/novell/sentinel/config/configuration.properties http.proxyHost=<proxy host/ip> http.proxyPort=<proxy port> 4. In configuration.properties file, set the value of http.nonProxyHosts to pipe separated host addresses for which you don’t want the connection to go through a proxy. This means that sentinel makes direct connection to these configured hosts rather using proxy. By default this should contain loopback, local sentinel ip, host info of any distributed targets configured, host info of slink server, host info of scm server as these should not go through a proxy. Host details can contain wildcard characters(*.acme.com) and multiple host info should get separated by ‘|’ http.nonProxyHosts=127.0.0.1|<sentinelip>|<disttargetipip>|<slink server>|<scm server|<advisorserver> 5. Restart sentinel