We're preparing to release CRM 2016 for our company and have run into a problem with its Claims authentication using ADFS. We're a long time Microsoft ADFS user and currently running ADFS 3.0 on Windows 2012R2 servers.
What we see is that the CRM authentication is stepping on the MSISAuth cookie and not using the FedAuth cookie. What happens is that once we authenticate to CRM, the MSISAuth cookie is overwritten and therefore we can no-longer authenticate to any new sites as we're sending a bad MSISAuth cookie. If we logout out of CRM, we can then again authenticate to a new site, but we are prompted for credentials.
We're trying to figure out how we could have configured the CRM application in such a way that it steps on the MSISAuth cookie and doesn't use the FedAuth cookie.
This is a serious usability issue for our company as once we login to CRM, we can no-longer login to any of our other ADFS authenticated applications until we log out of CRM. We have about 25 ADFS authenticated applications. What the users experiences is when trying to access a new sites is that the ADFS forms authentication page just keeps prompting for their logon credentials.
Is this a CRM configuration issue?, a CRM authentication problem? or some other issue? I would think that Microsoft would make integration between CRM Claims Authentication and AFDS fool proof, but what we're seeing is bad behavior in the CRM application. Hope there is a fix for this.
Thanks Dan
