It appears configuring merchants and acquirers is rather confusing, since users don't always get there are two public certificates in play: the merchant's and the acquirer's. Extra validation that makes sure the configured merchant key and certificate are a pair would make sure the user knows if he accidentally configured the acquirer's certificate for the merchant.

CommentFileSizeAuthor
#1 ideal_validate_private_key_public_certificate_against_eachother_00.patch1.03 KBxano

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Assigned: Unassigned » xano
Status: Active » Fixed
StatusFileSize
new ideal_validate_private_key_public_certificate_against_eachother_00.patch1.03 KB

Committed and pushed to 7.x-2.x.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Assigned: xano » Unassigned