Allow saving gateway forms with fake/incorrect API keys

Created on 17 February 2024, 9 months ago

Problem/Motivation

It would be useful to be able to save the payment gateways without needing to have the secret values saved in the gateway form. This can happen when e.g. you're storing the API keys via a secret settings file that isn't stored in the repository and want to store something like "CHECKTHESETTINGSFILE" in the config form.

Proposed resolution

Provide a way of saving the gateway form with invalid API keys.

Remaining tasks

Work out the best approach to allow the form to be saved with invalid / fake values.
Make the necessary changes.

User interface changes

The settings form can be saved without any changes.

API changes

n/a

Data model changes

n/a

✨ Feature request
Status

Active

Version

1.0

Component

User experience

Created by

πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @DamienMcKenna
  • πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

    What I've had to do is to disable the API checks in ExpressCheckout::validateConfigurationForm() and Checkout::validateConfigurationForm(), then I can manually tweak the configuration via the yml files.

Production build 0.71.5 2024