Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Loading

Publishing ADFS 2.0 using ISATMG

The following Steps should help you publish ADFS over ISATMGIAGUAG

First Open ISATMGUAGIAG
Right-Click Firewall Policy -> New-> Web Server Publishing Rule:

  1. Enter Publishing Rule Name: Federated Services
  2. Select Next through the next screens unless you are load balancing
  3. Enter the name of the URL (suggest this to be the same as the external URL and the IP of the server
  4. For the path /adfs/* select Forward host header
  5. Enter public name and  the same path
  6. Create a new listener:
  • Add Certificate
  • Always authenticate No
  • Domain for authentication: domain name
  • Authentication Method: No Authentication
  • Port 443 and 80
  • Forward all HTTP to HTTPS
  • Network select external IP address
  • Click next
  • Authentication Method select: No delegation, and client can authenticate directly
  • Make sure all users are selected
  1. Click Finish. Then Edit the rule and change the following:
  • Select the Link Translation Tab, Uncheck the Apply Link translation to this rule.
  1. Right Click The Rule and select HTTP and change
  • General Tab, uncheck Verify Normalization and Block high bit characters boxes
  1. Click OK and Apply changes

Alternatively:

Use the non-web server protocol publishing rule and select HTTPS Server as the protocol.

If the default HTTPS Server protocol still doesn’t work, create a new protocol using port 443 so that the Filter is completely bypassed

One thought on “Publishing ADFS 2.0 using ISATMG

  1. Thank you very much for this post. It really helped us in fixing the problem with ADFS behind TMG. wonderful post. thanks again.

Leave a Reply

Your email address will not be published. Required fields are marked *