Website under construction

Figure 2-85:
The Edit Claim Rules dialog box 
Note You will need to do this for each of your relying party trusts. 
URL hostname translation 
Another thing to keep in mind is that Web Application Proxy can translate host names in URLs. 
For example, you might have an application that your external users access by using the URL 
http://www.contoso.com/app01, whereas your internal users get to the same app by going to 
http://apps.contoso.com/app01. This is perfectly acceptable, and Web Application Proxy can 
handle the difference in the URL, as illustrated by Figure 2-86, in which the external URL is 
http://www.contoso.com/app01 and the Backend Server URL is http://apps.contoso.com/app01. 
Figure 2-86:
Published web applications 
Note You cannot change the path to be http://www.contoso.com/app1 externally and 
http://apps.contoso.com/applicationXYZ internally. 
This is valuable to know when publishing Exchange, because you can have different DNS namespaces 
for internal and external access. Therefore, you might want to publish a URL for Outlook Web App 
that is different for your internal users than the one you publish for external access. Figure 2-87 shows 
that Web Application Proxy can accommodate this need as long as you keep the same path name. 

---

82 
CHAPTER 2 | Software-defined datacenter 
Figure 2-87:
The publishing settings for an app 
To allow this type of translation, you first must get the ID of the application for which you want to 
implement translation. To do this, you can use the following Windows PowerShell command: 
Get-WebApplicationProxyApplication | Format-Table ID, Name, ExternalURL 
Figure 2-88 presents the output that results. 
Figure 2-88:
Output for Get-WebApplicationProxyApplication 
Next, take the application ID from the output shown in Figure 2-88 and then enter the following 
Windows PowerShell command: 
Set-WebApplicationProxyApplication –ID 
-DisableTranslateUrlInRequestHeaders:$false