You can configure the TMG Server to operate with the 10g ISAPI Webgate for Access Manager.
Task overview: Configuring the TMG 2010 Server for the ISAPI 10g Webgate
After resetting ISAPI Webgate permissions, you need to register Access Manager
postgate.dll plug-ins as Web Filters within Forefront TMG Server.
Web filters screen all HTTP traffic that passes through the TMG Server host. Only compliant requests are allowed to pass through. The following procedure describes how to register Access Manager plug-ins in the TMG Server.
To undo the filter registration, you can use the following procedure with the
/u option in the
regsvr32 command. For example:
regsvr32 /u TMG_install_dir\access\oblix\apps\webgate\bin\webgate.dll
To register Access Manager plug-ins as TMG Server Web filters
net stop fwsrvto stop the TMG Server.
webgate.dllas an ISAPI Web filter by running:
postgate.dllas an ISAPI Web filter by running:
net start fwsrv.
It is important to ensure that the Webgate ISAPI filters are included in the right order.
postgate.dll should be loaded before
To order the Webgate ISAPI filters for TMG Server
You need to ensure that the published Web site is accessible using the TMG proxy and verify that form-based authentication is working.
TMG supports both Basic over LDAP and Form-based or Basic authentication. You can choose the desired authentication scheme. TMG need access to
login.html, which you configure as described here.
To verify that form-based authentication is working
land click OK.
Stop Firewall Service use the command net stop fwsrv
Start Firewall Service use the command net start fwsrv