Donnerstag, 14. Juli 2011

HTTP to HTTPS Redirection Options in Forefront TMG and UAG

When publishing SSL-protected web sites such as Microsoft Outlook Web App with Forefront Threat Management Gateway (TMG) 2010 or Unified Access Gateway (UAG) 2010, it is often desirable to allow clients to enter the URL of the site without specifying the HTTPS protocol explicitly. For example, when publishing Outlook Web App (OWA) 2010 where the full URL is, for convenience an administrator might want to redirect non-secure requests for to use the secure HTTPS protocol automatically. This can be done in a number of ways, depending on which Forefront solution is used for publishing.
Forefront TMG
With TMG, HTTPS redirection can be enabled by opening the properties of the web listener used in the publishing rule and selecting Enable HTTPS connections on port: and Redirect authenticated traffic from HTTP to HTTPS.
Now when users request the non-secure they will automatically be redirected to the secure
Even more convenient is to redirect requests for the base URL to the correct path The easiest way to accomplish this is to create a new publishing rule that denies requests to and redirects them to To enable this functionality, use the Web Site Publishing Wizard to create a publishing rule that denies access to redirects those requests to
Be sure to place this rule before the publishing rule allowing access to the SSL-protected web site.
Now when users request the non-secure they will automatically be redirected to the secure
Forefront UAG
Configuring Forefront UAG to redirect HTTP to HTTPS is even simpler. After you’ve created a trunk and published OWA, right-click HTTP Connections in the UAG management console navigation tree, select New Trunk, and then select the HTTP to HTTPS redirection option.

Keine Kommentare:

Kommentar veröffentlichen

Rename Onedrive Business root folder

Rename Onedrive Business root folder Here is what I remember: In the Office 365 web admin pages, change the organization name to a shorte...