Troubleshooting an issue a user was having with my LinkedIn Company Updates Joomla module, I couldn’t replicate his issue. He had correctly followed the instructions outlined in the module, but was receiving a “null” message when he enabled Debug Mode.
He was gracious enough to give me access to his LinkedIn Developer Account so I could create the module in my server environment with his Company ID and it worked every time. However, my server environment uses an SSL certificate and his did not. So I created a new module parameter called “Disable SSL Check”. When this setting is enabled, I add the following lines to my cURL request:
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
$ch = curl_init();
This solved the problem. That said, in nearly every circumstance, it is highly recommended to keep the SSL check enabled in production. But, having gone through the entire process of verifying authorization codes and access tokens, this HTTPS v HTTP discrepancy in our server environments may have had an impact on functionality.