You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since August 2018, the Authorize.Net API has been reorganized to be more merchant focused. Authorize.Net AIM, ARB, CIM, Transaction Reporting, and SIM classes have been deprecated in favor of `net\authorize\api`. To see the full list of mapping of new features corresponding to the deprecated features, see [MIGRATING.md](MIGRATING.md).
45
+
Since August 2018, the Authorize.Net API has been reorganized to be more merchant focused. Authorize.Net AIM, ARB, CIM, Transaction Reporting, and SIM classes have been deprecated in favor of `net\authorize\api`. To see the full list of mapping of new features corresponding to the deprecated features, see [MIGRATING.md](MIGRATING.md).
29
46
30
47
### Contribution
31
-
- If you need information or clarification about Authorize.Net features, create an issue with your question. You can also search the [Authorize.Net developer community](https://community.developer.authorize.net/) for discussions related to your question.
48
+
- If you need information or clarification about Authorize.Net features, create an issue with your question. You can also search the [Authorize.Net developer community](https://community.developer.authorize.net/) for discussions related to your question.
32
49
- Before creating pull requests, read [the contributors guide](CONTRIBUTING.md).
33
50
34
51
### TLS 1.2
@@ -68,7 +85,7 @@ Authorize.Net maintains a complete sandbox environment for testing and developme
API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.
88
+
API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.
72
89
73
90
## SDK Usage Examples and Sample Code
74
91
When using this SDK, downloading the Authorize.Net sample code repository is recommended.
@@ -127,27 +144,22 @@ To create the javadocs:
127
144
### Testing Guide
128
145
For additional help in testing your own code, Authorize.Net maintains a [comprehensive testing guide](http://developer.authorize.net/hello_world/testing_guide/) that includes test credit card numbers to use and special triggers to generate certain responses from the sandbox environment.
129
146
130
-
## Logging Sensitive Data
131
-
132
-
The Authorize.Net Java SDK uses Log4J framework for logging purposes. Enable the logger by keeping a configuration file `Log4j.properties` in the resources folder of the application. A sample [Log4.properties](https://github.com/AuthorizeNet/sdk-java/blob/master/resources/log4j.properties) file has been provided as a reference.
133
-
134
-
The possible log levels are `DEBUG, INFO, WARN, ERROR` and `FATAL`. There is a new pattern layout introduced to mask sensitive data while logging and can be used with the application by providing the following configurations in the `Log4j.properties` file:
135
-
136
-
```
137
-
// Default configuration which logs the entries in clear text
By default the logger comes with two appenders, **console** and **file transport**.
150
-
147
+
## Logging Sensitive Data
148
+
149
+
The Authorize.Net Java SDK uses Log4J2 framework for logging purposes. Enable the logger by keeping a configuration file `log4j2.xml` in the resources folder of the application. A sample [log4j2.xml](https://github.com/AuthorizeNet/sdk-java/blob/master/resources/log4j2.xml) file has been provided as a reference.
150
+
151
+
The possible log levels are `DEBUG, INFO, WARN, ERROR` and `FATAL`. There is a new pattern layout introduced to mask sensitive data while logging and can be used with the application by making the following configurations in the `log4j2.xml` file:
152
+
153
+
1. Create your own appender under `<Appenders></Appenders>` and insert the `<PatternLayout><pattern></pattern></PatternLayout>` section. (Example is present in the `log4j2.xml` file)
154
+
* To enable masking of sensitive data, replace `%m` with `%maskedMessage`.
155
+
* To disable masking, replace `%maskedMessage` with `%m`.
156
+
2. Create a logger under `<Loggers></Loggers>`
157
+
3. The `name` field in the `<Logger>` should contain the namespace from where log messages needs to be written to file.
158
+
4. Attach an `<AppenderRef>` section where the `ref` field uses one of the Appenders that have been created under the `<Appenders>` section.
159
+
5. Do **NOT** modify the logger with `<Root>`.
160
+
161
+
By default the logger comes with two appenders, **LogToConsole** and **RollingFile**.
162
+
151
163
The sensitive fields that are masked during logging are:
152
164
* Card Number
153
165
* Card Code
@@ -156,7 +168,7 @@ The sensitive fields that are masked during logging are:
156
168
* Account Number
157
169
* Name on Account
158
170
159
-
There is also a list of regular expressions which the sensitive logger uses to mask credit card numbers while logging.
171
+
There is also a list of regular expressions which the sensitive logger uses to mask credit card numbers while logging.
160
172
161
173
More information on the regular expressions used during sensitive data logging [can be found here](https://github.com/AuthorizeNet/sdk-java/blob/master/resources/AuthorizedNetSensitiveTagsConfig.json).
0 commit comments