Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Logging Mechanism inadvertently Storing CC info #48

Closed
fogeytron opened this issue May 20, 2015 · 3 comments
Closed

Using Logging Mechanism inadvertently Storing CC info #48

fogeytron opened this issue May 20, 2015 · 3 comments

Comments

@fogeytron
Copy link

Hi,

We are using CIM and are using Auth.net to handle storing all of our CC info.

We are also using the built in logging mechanisms in the SDK to troubleshoot any issues we have.

The problem is that when you make a createCustomerPaymentProfileRequest, one of the fields is the CC number so that is stored in plain text in the log file.

Is there anyway you could update the logging to mask the actual CC number and cvv code so we can continue to use the logging, but also not have access to the sensitive data?

@brianmc
Copy link
Contributor

brianmc commented May 21, 2015

We're on it, thanks @fogeytron

@gRegorLove
Copy link

Any progress on this? This is a pretty crucial bug. I'm holding off switching from AIM to Authorize.net API at the moment due to this.

@brianmc
Copy link
Contributor

brianmc commented Feb 1, 2016

This was fixed in the last release: 1.8.6.2, apologies for not updating the issue.

@brianmc brianmc closed this as completed Feb 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants