Share
Report
215Recently a CRM 2016 Online customer reported that their Outlook plugin was no longer connected to CRM. We determined that IT had added some new web proxies to the network. It was these new proxies causing the problem as the Network team wrote below. Has anyone heard of this and know if it's possible to change how the plugin to pass the user's credentials as they describe below? Never heard of this, thanks.
Issue: New proxies have the ability to inspect SSL traffic. This was not the case on the old system. One such rule is that SSL connections require authentication to go through, when routed explicitly. We have seen in other systems, as well as in this case, the clients, and specifically for this, the Outlook plugin was not passing the user's credentials, so the site was failing.
We need to get the vendor to configure the client to pass the logged-in user's credentials. Once that is in place we can remove the bypass and return to a better security posture. So it works now. It would be great if you could work with the vendor to get the credentials to pass.
Temporary Fix: Bypass the requirement for SSL traffic going to crm.dynamics.com to require authentication. We lose visibility when doing so. My whitelisting opens up this crm farm across the board - for every site they host. Not a good thing.
*This post is locked for comments
All responses (
Answers (
