Emailing PDF with SSPI Failed After Online Charging Using Credit Card
ERROR: A call to SSPI failed, see inner exception.
The client and server cannot communicate, because they do not
possess a common alogrithm
See sample screen below:
If I just email the PDF file without charging a credit card, then this error does not happen. Please advise.
A - After thorough investigation of this issue, it can happen if a user chooses to enable SSL with SMTP email, and the email server does not support TLS 1.2 communication. See sample screen below on "Enable SSL with SMTP Email."
When the credit card is charged in Elliott, Elliott communicates with Payware Connect Payment Gateway servers by using TLS 1.2 communication protocol. This is a requirement as of Elliott 8.1 release. This elevates the subsequent communication to require TLS 1.2 support. In this case, the SMTP service is hosted by an Exchange server residing on a Windows 2003 server. The Windows 2003 server does not support TLS 1.2 communication. Thus we receive this error.
There are couple ways to solve this problem:
- Do not use SSL in Elliott SMTP settings. In this case, the Exchange server is hosted in-house. The SMTP communication only goes through the local LAN so using SSL protocol for security is unnecessary. Keep in mind that this is a special case. If you use a hosted email service outside your LAN, then you should consider using SSL. But most likely, those hosted email servers will already support TLS 1.2 communication, so it is not an issue with SSL being turned on in that case.
- Solution 1 above is the best and easiest solution. If, for whatever reason, you still want to use SSL with an internal STMP server, then ask your user to exit Elliott after the credit card operation. Then, start up Elliott to continue the emailing of the PDF file.
- Alternatively, you can use a different SMTP server that supports TLS 1.2. Any Windows server can also act as an SMTP server. You just need to choose a Windows server version on or after 2008 R2 release.
- Consider migrating your Exchange server to a Windows server that supports TLS 1.2 (i.e., Windows 2008 R2 and up).
EMK