Page MenuHomePhabricator

Network configuration for Civiproxy
Closed, ResolvedPublic

Description

We need firewall config and server config to allow frdata (email-pref-center-wiki) web servers (but not the internet at large) to make requests to the civicrm hosts on the port which will serve civiproxy

Can payments servers just make the requests to civicrm.wikimedia.org, or is there a different alias they should use internally?

FR-Tech-Ops Notes:

  • civiproxy will be exposed internally as https://{civicrm app server fqdn}:442 - this configuration should come from puppet not localsettings
  • [need to confirm this] it will be accessible only to donorwiki running on the frdata server role
  • civiproxy service needs access to redis on frqueue server role
  • civiproxy service needs access to civicrm on localhost/loopback (this is relevant for container/firejail)

Event Timeline

@Ejegg As far as I know the only server/service planned to access civiproxy is donorwiki, which will run on the frdata servers. Is that what this task is about, and not payments servers?

@Ejegg As far as I know the only server/service planned to access civiproxy is donorwiki, which will run on the frdata servers. Is that what this task is about, and not payments servers?

Oops, yep, that's the one. I had momentarily forgotten that email pref center was a separate wiki when I wrote this task. Updated!

Dwisehaupt moved this task from In Progress to Done on the fundraising-tech-ops board.

All of the iptables and pfw rules have been pushed. Basic connectivity verified. On to testing all the functionality.