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
@@ -61,6 +61,7 @@ You do not need to download and build the source to use the SDK but if you want
61
61
- if `enablejdkcert` parameter is set to true, certificates will be read from the JKS file specified at keysDirectory location. The JKS file should be of the same name as specified in keyFilename.
62
62
- To know how to convert p12 to JKS refer the JKS creation section of this document.
63
63
-`enableCacerts` property is considered only if `enablejdkcert` is set to true. If `enableCacerts` is set to true, certificates will be read from the cacerts folder under the JDK.
64
+
- if `certificateCacheEnabled` parameter is set to false (default is true), the p12 certificate of a merchant will be reloaded from filesystem every time a transaction is made
64
65
-`allowRetry` config parameter will only work for HttpClient. Set `allowRetry` config parameter to "true" to enable retry mechanism and set merchant specific values for the retry.
65
66
- Set integer values for config parameter `numberOfRetries`*and*`retryInterval`. Retry Interval is time delay for next retry in seconds.
66
67
- Number of retry parameter should be set between 1 to 5. Any other value will throw an Error Message.
@@ -181,12 +182,12 @@ Retry Pattern allows to retry sending a failed request and it will only work wit
181
182
182
183
## Changes
183
184
184
-
Version Cybersource-sdk-java 6.2.5 (OCT,2017)
185
+
Version Cybersource-sdk-java 6.2.6 (OCT,2017)
185
186
_______________________________
186
187
1) Merchant cert to be read from JAVA key store. Flag is added to enable reading cert from Java keystore.
187
188
2) Added Custom HttpClient feature. Merchants can use there own http client instead of defaults which comes with SDK.
188
189
3) Http Client connection reuse issue.
189
-
4) Changed clientLibrary version to 6.2.5; in 6.2.4 release it was missed. So, in 6.2.4 release, clientLibrary version was pointing to 6.2.3.
190
+
4) Changed clientLibrary version to 6.2.6; in 6.2.4 release it was missed. So, in 6.2.4 release, clientLibrary version was pointing to 6.2.3.
0 commit comments