HTML Forms Authentication or Forms-based logon is likely familiar to most TMG administrators as it is often used in web publishing scenarios.
![forefront tmg 2010 owa publishing forefront tmg 2010 owa publishing](https://techgenix.com/content/isa/img/upl/image0321280601940935.jpg)
Microsoft Office 2010 Clients (excluding Outlook) It’s downside, one can argue, is that this approach may be less than satisfactory from a security perspective, with some form of pre-authentication at the edge more preferable.įor browser-based clients there are pre-authentication options with TMG, in conjunction with authentication delegation to the AD FS service that can be used. It’s simple and doesn’t “interfere” with the federation logon process like the other approachesdescribed. This scenario is called No Authentication as a reference to the fact that TMG isn’t performing any pre-authentication itself. The user request is proxied to the AD FS server and the AD FS picks up the logon request. With no AD FS proxy present, the TMG is setup to reverse proxy traffic to the AD FS backend.
FOREFRONT TMG 2010 OWA PUBLISHING PASSWORD
![forefront tmg 2010 owa publishing forefront tmg 2010 owa publishing](https://techgenix.com/content/mse/img/upl/image0061318015957890.jpg)
In the meantime, there are a few TMG front-end pre-authentication methods/combinations to try out with O365 and AD FS 2.0.Īs the diagram above illustrates, TMG supports a number of authentication types.
![forefront tmg 2010 owa publishing forefront tmg 2010 owa publishing](https://richardhicks.files.wordpress.com/2011/01/http_https_02.jpg)
I believe Microsoft at some point will expand on the supported TMG scenarios for O365 and how these options work in conjunction with AD FS 2.0. Let’s have a look at some of the authentication methods/options that are possible with TMG, Federation and Office 365.