Integration with the Key module would allow site administrators to choose how the Authorize.net transaction key is stored—in a file outside the web root, for instance, or on another server altogether. This would allow for a greater level of security than storing the key in plaintext in the database.

The Key module is still in development, but I wanted to get the conversation started for how Commerce Authorize.Net could take advantage of its functionality. See the attached screenshot for an example of how choosing a key could appear in Commerce Authorize.Net's settings.

Comments

rlhawk’s picture

Status: Active » Needs review
StatusFileSize
new2.81 KB

Here is a patch that adds support for the Key module, which is currently at 7.x-1.0-beta2.

rlhawk’s picture

Status: Needs review » Closed (won't fix)

I've changed the way integration with Key works, so this issue and patch are no longer applicable.

rlhawk’s picture

Status: Closed (won't fix) » Needs review
StatusFileSize
new1.55 KB

Reopening with a new patch to add integration with the Key module.

rlhawk’s picture

Status: Needs review » Needs work

The Key module is currently being refactored. A new patch will be submitted when ready.

nicksanta’s picture

Issue tags: +key-integration

Added key-integration tag to track integration efforts across contrib.