https not working on SuiteCRM Outlook Plugin v1.1.0.9?

I have did some testing on SuiteCRM 7.6.6 with the SuiteCRM Outlook Plugin v1.1.0.9, when I entered http for the URL in the Credential setting, the account can login successfully (see attached 1.png), but when I entered httpsfor the URL in the Credential setting and test the login, the SuiteCRM Outlook Plugin prompted “The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.” (see attached 2.png)

However, the https URL for the SuiteCRM was actually working, I can open its login page on Internet Explorer (see attached 3.png) though its certificate is self generrated by IIS.

My question is, is that the SuiteCRM Outlook Plugin not support the self generated certificate?

kwli,

Same problem here… did you ever find a solution? Or does anyone else have a solution? Also, has anyone tested with an authority-signed certificate instead of a self-signed certificate? I, like kwli, am currently using a self-signed certificate, but I’ve been thinking about purchasing one.

sieberta

I have reported this as a bug: https://github.com/salesagility/SuiteCRM-Outlook-Plugin/issues/22

I do believe this is due to a self signed certificate, and I suspect this is related to a library used in the plugin… perhaps using C#?

http://stackoverflow.com/questions/703272/could-not-establish-trust-relationship-for-ssl-tls-secure-channel-soap

I opened IE and navigated to my https:// and then clicked the “Certificate” error in the address bar.
I then clicked “Install Certificate”
Current User
Place the certificate in the following store: “Trusted Root Certificate Authorities”

Then complete the wizard. I’m still getting an error message, but it is different…
“Unexpected character encoutered while parsing value: <. Path ‘’, line 0, position 0.”

More information on that in this thread: https://suitecrm.com/forum/suitecrm-outlook-plugin/7265-unexpected-character-encountered-while-parsing-value-path-line-0-position-0

So that could be unique to me (i.e. some other problem unrelated to the certificate…