Website under construction

1.
WAP stops the request and passes all credentials to AD FS. 
2.
AD FS validates, applies policy, and replies with a token. 
3.
Upon success, Web Application Proxy allows the request to pass to the Exchange server. 
4.
Web Application Proxy caches the token for future use. 
The third option is OAuth2, which is an authorization framework that many vendors use, including 
Microsoft. Web Application Proxy has supported OAuth2 since Windows Server 2012 R2; however, the 
option was not available in the user interface (UI). 
More info To learn more about OAuth2, go to 
http://tools.ietf.org/html/rfc6749
. You can find 
additional information about AD FS support for OAuth2 at 
http://technet.microsoft.com/ 
library/dn383640.aspx
. 
After you select the appropriate client for the publication, click Next. The Publishing Settings page 
includes one new option with which you can turn on HTTP-to-HTTPS redirection, as illustrated in 
Figure 2-75. 
Figure 2-75:
Publishing settings 
This is a great addition because to turn on HTTP-to-HTTPs redirection in Windows Server 2012 R2, 
you were required to install and configure Internet Information Services (IIS). Notice that this option is 
selected by default, but ensure that it is selected for your app before clicking Next and moving on to 
the Confirmation page. 
Remote Desktop Gateway scenario 
The changes that were first introduced in the Windows Server 2012 R2 August 2014 update package 
regarding the way Web Application Proxy handles Remote Desktop Gateway publication is 
incorporated in this release. This change simplifies the deployment experience for IT administrators 
who are planning to publish RDP via Web Application Proxy and makes it possible for Remote 
Desktop Gateway to pick up the session cookie that was used by Remote Desktop Web Access to 
authenticate the RDP over HTTP traffic. 

---

75 
CHAPTER 2 | Software-defined datacenter