When testing on a local dev server using a self signed SSL certificate on IIS7, the SendConfirmationEmail checkout pipeline task fails giving the following exception:
Outer exception Exception occoured while processing pipeline 'UCommerce.Pipelines.Checkout.CheckoutPipeline'. See inner exception for details.
Inner Exception The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
I'm believe this is due to using a test certificate and the request to the template page for the email content being sent via the current (HTTPS) protocol. Is there any way of requesting the email content from HTTP rather than HTTPS or is this just 'fact-of-life'?
uCommerce will use the base URL to request the e-mail body, i.e. if you're requesting from a secure connection uCommerce will do the same. If on the other hand you execute the checkout pipeline on a non secure URL you won't have the problem.
Our EmailService is not pluggable today so that behavior is a fact of life as it stands.
Checkout pipeline: SendConfirmationEmail
When testing on a local dev server using a self signed SSL certificate on IIS7, the SendConfirmationEmail checkout pipeline task fails giving the following exception:
Outer exception
Exception occoured while processing pipeline 'UCommerce.Pipelines.Checkout.CheckoutPipeline'. See inner exception for details.
Inner Exception
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
I'm believe this is due to using a test certificate and the request to the template page for the email content being sent via the current (HTTPS) protocol. Is there any way of requesting the email content from HTTP rather than HTTPS or is this just 'fact-of-life'?
Hi James,
uCommerce will use the base URL to request the e-mail body, i.e. if you're requesting from a secure connection uCommerce will do the same. If on the other hand you execute the checkout pipeline on a non secure URL you won't have the problem.
Our EmailService is not pluggable today so that behavior is a fact of life as it stands.
Cheers Søren. Guess I'll be setting up the web.config for conditional SSL after all :-)
is working on a reply...