![]() ![]() ![]() Retrieval of proxy config data from federation server using trust certificate with thumbprint failed with status code unauthorized. The federation server proxy configuration could not be updated with the latest configuration on the federation service. The one which mostly got my attention was the 224: There were couple of errors related to the certificate and Service issue, Event ID 224, Event ID 12025, Event ID 7023 and Event ID 224. The errors related to the service not starting in the event viewer were all pointing to a certificate thumbprint which didn’t even exist in the WAP’s personal store.I solved this by pointing the machine to the secondary DC and add the ADFS hostname to the host file.Ģ- The Web Application Proxy Service would not start. In my environment where we are using Sentinel, We have isolated the primary DC in the environment and due to this the WAP server could not reach to the DNS Server.In this environment I am using WAP Proxy server behind ADFS and when installing this I configured a trust using a Public Certificate but for some reason this trust was broken.Īfter investigating the WAP proxy it seems it had couple of problems: 1- Could not resolve ADFS server name on WAP Server. If you are using Office 365 with ADFS Integration in place, You might get this error when trying to authenticate your users to login to Office 365 or any of its services. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |