Gr4vy provides a private key for authorising the API requests. I've created and downloaded this key into my home directory on the frpm host. We need to save this key in a dedicated credentials directory like we do for other keys.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T364501 Gravy Integration | |||
| Resolved | Dwisehaupt | T370159 Copy Gravy certificate to dedicated Cert directory |
Event Timeline
Comment Actions
@Damilare I have added the key to the private repo and can add it to the hosts. What hosts/roles is this needed on? The ones I would think as possibilities are: payments, civicrm, frdev
Also, is this going to require a new call out to an external network. If so, we'll need to open a ticket to track the iptables and firewall changes that are required.
Thanks.
Comment Actions
@Dwisehaupt I've created this phab T370319 for the network configuration and I've reached out to the Gr4vy team for their hostnames and IP ranges. As mentioned in the call today, the hosts that would be good to have access to the cert are payments, smashpig, civicrm, and frdev.
Comment Actions
The private key has been configured and is in place on the civicrm, frdev, payments, and payments-listener roles. The file is available at:
- /etc/fundraising/gravy_api_cert.pem
- /etc/gravy_api_cert.pem
Let me know if you have any issues or need it in more (or fewer) places.