I am trying to get a sandbox PayPal IPN working with the Coldfusion example shown here:
https://github.com/paypal/ipn-code-samples/tree/master/coldfusion
I've added the location of my IPN file to PayPal and the page is being called by it but all I get is a 'Connection Failure' message in the text file. The IPN file is being called from an https location so not sure what is wrong.
Any ideas?
The JRE (version 7) that comes with ColdFusion 10, doesn't support TLS 1.2, which you require to talk to the PayPal API. You need to either update the JRE to 113+ and enable TLS 1.2 via argument or upgrade altogether to JRE 8. To upgrade, you have to let the jvm.config point to the installation and replace the tools.jar in CF with the one from the JDK 8. (Also make sure to have at least update 14 installed on your ColdFusion 10 server.)
Related
I have installed Bugzilla 5.0.4 in Xampp 5.6.24-2-VC11 with ActivePerl 5.24.3.2404 and CAS plugins from https://bitbucket.org/triologygmbh/bugzilla-cas-plugin/src/master/
Changed User Authentication to CAS and CAS parameters to:
CASserver: https://xxx.xxx.xxx/cas
CASfullNameAttribute: id
CASmailAttribute: mail
CASTimeTolerance: 1000
Almost every features are working like login redirect to CAS server, redirect back to bugzilla, logout SSO. Its just when I get authenticated and redirect back to bugzilla. It gives File does not exist at loader/0x470db8/Bugzilla/Extension/CAS/Auth/AuthCASSaml.pm line 413
Anyone with experience of Bugzilla CAS or the plugin can help?
Update
For bugzilla 5.0.6
File does not exist: {"timestamp":1595816698854,"status":500,"error":"Internal Server Error","exception":"java.lang.NullPointerException","message":"No message available","trace":"java.lang.NullPointerException\n","path":"/cas/samlValidate"} at /loader/0x8c1578/Bugzilla/Extension/CAS/Auth/AuthCASSaml.pm line 413.
Update
Same error occur with latest xampp for both bugzilla versions
After I install the module and complete my API credentials I click the "save" button and I always get the following error:
Error !
You need to complete the PayPal identification Information in step 3
otherwise you won't be able to accept payment.
I already uninstalled and reinstalled the module.
PrestaShop version: 1.6.1.4
PayPal version: 3.10.6
Because of You install module that is unknown if it support PayPal's latest changes or not.
Seems like when You click save button it send CURL request to PayPal and tires to get necessary data. But response is not same as supposed to be.
If You're PHP dev: You've to debug that module,
otherwise: find someone to fix it.
I am setting up a website using osCommerce 2.3. The site is close to completion so I set up a PayPal sandbox to test the transaction/payment process. I am using the PayPal Express Checkout module provided with osCommerce. I inserted the sandbox username, password and signature into the module and tried the credentials test link. The test failed and the test debug email showed that no data was being transmitted by either $_GET or $_POST. Where do I go from here?
It turns out I am using WampServer 2.2.22, a 64-bit version which contains a buggy version of the curl.dll. Curl was refusing to load, so when it was making the call to PayPal in the sendTransactionToGateway function in paypal_express.php, the function failed. Working 64-bit versions of curl can be found at http://www.anindya.com/ for php 5.3.13 and 5.4.3. Replacing the old version of curl with the new one and restarting wampserver did the trick.
So I've been running CF9 on Linux for a while and using CFMail to send email through a client's Exchange 2010 server for quite a while.
We're attempting to migrate to CF10 on Win2008, IIS7.5. Everything is set and ready to go except I can't get CF10 to verify the mail connection? I've got both mail settings (CF9 and CF10) set the exact same way and can view them open side by side and verify they're identical. However, while the CF9 verifies successfully the CF10 system fails??
I tried sending through CFMail tags while specifying the server credentials and see this in the CF10 log:
"javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client"
What does this mean? I know my authentication credentials are correct because I'm able to connect in CF9.
I've turned off all firewalls and still nothing. So, I then tried installing CF10 on my Mac laptop. It, too, will not verify the mail connection!
Is there a known problem with CF10 connecting to an Exchange mail server?
Any ideas?
I "solved" this.
I could find little online and received no comments to this thread. No combination of settings I tried would work and I have no access to the client's mail server. The person who runs that server couldn't run a lemonade stand so no help there.
Then I stumbled across this page. Nothing to do with ColdFusion but seemed like a similar issue.
Recent changes in the JavaMail API has changed certain authentication
defaults and sometimes will create an authentication error with some
Exchange Server environments dependent on the configuration.
I'd never put much thought into CFMail because it was always drop dead simple and simply worked. Focusing on this link's Resolution 2 (ie replace the mail.jar with an older version). I wondered if CF used JavaMail and if I could downgrade CFMail? I cracked open CF's mail.jar file and found that CFMail does, indeed, use the JavaMail API. So, I then checked the ColdFusion docs to see if any new features were added to CFMail between CF9 and CF10. None.
So, I swapped out the mail.jar file from my CF9 install to CF10 and restarted. Boom! Everything worked immediately. As far as I can tell I've had no compatibility issues to report.
Swapping the mail.jar did not work for me. However, adding the following to JVM arguments
-Djava.net.preferIPv4Stack=true
worked for me. Please refer to the following article
Java Mail mystery - SMTP blocked?
posted by another user
Up until today, I have been successfully developing with PayPal's sandbox using the new PayPal PHP SDK which comes preconfigured to use this sandbox URL:
https://api.sandbox.paypal.com/2.0/
(URL in Chrome currently returns: "Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.")
But today my webapp is crashing due to a SSL handshake failure:
Uncaught exception 'PPConnectionException' with message 'error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure' in ./paypal-sdk-1.0.92/lib/PPHttpConnection.php:185
The only event that has occurred since yesterday (when my webapp was last working) was I reset my sandbox "seller" account, which may have reset the API credentials according to this post. Since I've updated the API credentials manually, and have verified them to be correct, I cannot say if they were ever wrong at this point.
After lots of searching, I found other web articles that say the URL should be:
https://api-3t.sandbox.paypal.com/2.0/
(URL in Chrome returns a SOAP response.)
So I changed my PayPal PHP SDK's included URL from https://api.sandbox.paypal.com/2.0/ to https://api-3t.sandbox.paypal.com/2.0/ and it is working perfectly again. What happened here? Is the non-"3t" sandbox URL simply broken right now?
EDIT: After the feedback received from #Win and #JoelP, I have filed a bug report through the PayPal SDK github so someone at PayPal can explain what changed today and fix the SDK to have the correct URL when using Signature credentials.
EDIT 2: PayPal fixed the issue a few days ago. It's going to be available in the next release. https://github.com/paypal/SDKs/issues/22#issuecomment-8660682
Thanks for the help everyone.
Differences are between Certificate and Signature
Signature is the preferred way of accessing PayPal API.
The issue is fixed and the code has been pushed to master branch. You should see the refreshed bundles of the sdk out on x.com in the next couple of days.
Refer GitHub issue here https://github.com/paypalx/SDKs/issues/22
Thanks,
Prasanna.
I can't answer the question but I can say that I have just discovered the same problem. I confirm that jimp's workaround of changing the SDK's service endpoint config to :
service.EndPoint="https://api-3t.sandbox.paypal.com/2.0/"
solved my issue. (This is in the Paypal SDK config/sdk_config.ini file).
In my case I am using the PHP SDK. I have not changed anything on my sandbox account. My best guess is that the original URL is simply down for a while. (Firefox shows the "Secure Connection Failed" alert).