Skip to main content
eriku40433679
Level 3
Jun 17, 2019 6:11 AM UTC
Solved

Webapps behind an ip whitelist

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.
    Jonathon_wodnicki
    Jonathon_wodnickiAccepted solution
    Community Advisor
    Jun 18, 2019 5:28 PM UTC

    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

    View in thread

    2 replies

    Jonathon_wodnicki
    Community Advisor
    Jonathon_wodnickiCommunity AdvisorAccepted solution
    Community Advisor
    Jun 18, 2019 5:28 PM UTC

    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

    Translate
      eriku40433679Author
      Level 3
      Jul 12, 2019 4:29 AM UTC

      Thank you for the help Jon! This is wonderful.

      Cheers,

      Erik

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...