Hello All,
We seem to be having an issue during the setup of the IFD and would appreciate any assistance for where the problem may be.
Servers:
- Server 2012 R2 - DC (running ADFS 3.0)
- Server 2012 R2 - CRM Front-end
- Server 2012 R2 - CRM Back-end
- Server 2012 R2 - SQL
DNS (Hybrid/Split):
- On-premise: internal.domain.com (primary) / domain.com (added second primary lookup zone)
- Off-premise (hosting provider): domain.com
Our A-record entries are located in the second primary "domain.com" lookup zone:
- adfs (sts) - DC
- auth - front-end
- dws (dev) - front-end
- internalcrm - front-end
SSL wildcard certificate for *.domain.com purchased through Comodo.
We have setup claims-based authentication with no problems except from Chrome (which we remedied by disabling the extended protection token check and adding user agent for NTLM authentication).
Though after successfully getting claims-based auth functioning without any issues, as soon as we complete the IFD configuration and add the relying party trusts. We then seem to loose the ability to connect internally, receiving an ADFS error page.
Now, we are unsure if this due to our current domain setup or if this is something to do with the steps we have taken to configure the IFD.
We have been using these two guides for what applies to our current setup:
InteractiveWebs & Niran Belliappa MSDN Blog
Any help would be hugely appreciated! Thank you
