![]() On the WAP server, EventID 422 was logged into the AD FS Admin log stating that it was unable to retrieve proxy configuration data from the Federation Service. ![]() On the WAP server, the Remote Access Management Console was not happy. Starting Point – What The AD FS Proxy Saw It does not aim to cover AD FS 2.0 or 2.1 at all. Please note that this post is specific for AD FS 2012 R2. How do we fix this? Actually before we dive into that, lets see what was going on first. The internal AD FS server was OK, the issue was just with the proxy. At this point the AD FS Proxy was “dead to me” as far as the AD FS server was concerned. The AD FS Proxy was not contacting the AD FS server on the internal network, and this allowed the short lived authentication certificate to expire. They let the AD FS 2012 R2 proxy get into a bad state. In the Tailspintoys environment, the administrator (moi) was a bit slack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |