Solved

ADFS not behaving as expected through load balancer

Posted on 2013-10-28
2
849 Views
Last Modified: 2013-11-01
We are experiencing a very strange problem with our ADFS Environment.

When we connect to our ADFS Landing Page at https://adfs.mydomain.com and click the “Sign In” Button, something happens to make our workstations query DNS for a server other than adfs.mydomain.com.

This is shown in Fiddler in the highlighted portion at the lower right (shown below) where I see <h2> Object moved to <a href=’https://server-119.mydomain.com/adfs.ls/?SAMLRequest=…

See the fiddler analysis below.

Fiddler Screenshot
      
How all of our 100+ websites behave
      

1.

User enters the URL https://mywebsite.mydomain.com into their web browser to access the one of our websites.

2.

User successfully arrives at the website using that URL.

3.

User signs into the website, or clicks some links to go to other parts of the website.

4.

The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename1.htm

5.

User clicks more links on the website.

6.

The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename2.htm

7.

User clicks more links on the website and performs some complex tasks on the website.

8.

The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename3.htm      
How all 100+ of our websites work
How our ADFS Website Behaves - which is totally different than all our other websites

1.

User enters the URL https://adfs.mydomain.com/adfs/ls/IdpInitiatedSignOn.aspx into their web browser to access the ADFS Landing Page.

2.

User successfully arrives at the ADFS Landing page via that URL.

3.

User clicks the "Click Continue to Sign In Button" on the ADFS Landing Page.

4.

Something, most likely code on that landing page or somewhere else inside the ADFS Server, sends back information to the web browser with the name http://server-119.mydomain.com.

5.

The User's computer then queries DNS for http://server-119.mydomain.com 

6.

The User's web browser then access http://server-119.mydomain.com directly and no longer goes through the load balancer.
How the ADFS Website Does Not Behave Like all the others.
This is my problem.

I have a feeling that ADFS has done something to IIS that is making IIS behave differently when ADFS sits inside of it, when compared to every other IIS website we have.

That’s what I need to get to the bottom of .
0
Comment
Question by:ACECORP
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 20

Accepted Solution

by:
compdigit44 earned 500 total points
ID: 39610311
Interesting...

In IIS have your check your site binding and redirect settings?

Do you have any external DNS Cname records points to there other server name?
0
 
LVL 5

Author Closing Comment

by:ACECORP
ID: 39617526
I had to rip the environment down and rebuild it. I had to make a lot of changes, to many to list here, but I solved it :)

Thanks for your efforts.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article explains the steps required to use the default Photos screensaver to display branding/corporate images
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question