Webapps behind an ip whitelist | Community
Skip to main content
Level 3
June 17, 2019
Solved

Webapps behind an ip whitelist

  • June 17, 2019
  • 2 replies
  • 1960 views

Hi,

We have an on-premise installation of campaign and have a whitelist set up on the load balancer so only select ip addresses get to log in and use it. The approach however, prevents webapps from being publicly accessible. Is there a way for us to safely expose the /webapps easily or is this more an OPS/IT question rather campaign? I can only think off setting up Apache with modproxy on some box who's ip has been whitelisted on the elb. Anyone got a similar set up? How would the open/link tracking have gone through if this was the case?

Thanks,

--Erik

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jonathon_wodnicki

Hi,

You can use mod_proxy to whitelist IP address/URL combinations, or configure Campaign's web module to do same:

Almost all of Campaign's internal traffic is to /nl/jsp/soaprouter.jsp (block for inbound from internet).

Thanks,

-Jon

2 replies

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
June 18, 2019

Hi,

You can use mod_proxy to whitelist IP address/URL combinations, or configure Campaign's web module to do same:

Almost all of Campaign's internal traffic is to /nl/jsp/soaprouter.jsp (block for inbound from internet).

Thanks,

-Jon

Level 3
July 12, 2019

Thank you for the help Jon! This is wonderful.

Cheers,

Erik