Unfortunately, the ability to make use of the Web Application Proxy comes with a pretty awkward requirement: you must have AD FS installed in your environment to be able to use i—even to test it, because the WAP configuration is stored inside AD FS. None of the WAP configuration information is stored on the Remote Access Server itself, which makes for a lightweight server that can be easily moved, changed, or added to. The downside to this is that you must have AD FS running in your environment so that WAP can have a place to store that configuration information.
While a tight integration with AD FS does mean that we have better authentication options, and users can take advantage of AD FS single-sign-on to their applications that are published through WAP, so far this has proven to be a roadblock to implementation for smaller businesses. Many folks...
