Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 188
  • Last Modified:

Configure ADFS and ADFS proxy procedures

Hi

Does anyone have any good procedures fo rconfiguring ADFS and ADFS proxy?

I am setting them up in a lab environment with a view to add resiliency servers for each of them later and set up NLBs.

At this stage, i have set up SSL cert and installed ADFS 2.0 on SRV2008R2 (all green ticks).

I need help configuring the AD trust (the single sign-on web page) as well as linking ADFS proxy into ADFS.

The environment will eventually be used for office 365, but for now i just need to set up the ADFS sided of things, add resiliency and prove it works.

Could anyone point me in the right direction?

Thanks

Mihail
0
mk112233
Asked:
mk112233
1 Solution
 
MaheshArchitectCommented:
1st of all setup ADFS 3.0, not 2.0

ADFS 3.0 have built-in sign in page for you
Check below thread and my answer to clarify
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_28601682.html

Once you setup ADFS run below web page and see if it open up metadata XML as appropriate, you might need to add url into "Compatibility view settings"
https://adfs.domain.com/federationmetadata/2007-06/federationmetadata.xml

Also run below url:
https://adfs.domain.com/adfs/ls/idpinitiatedsignon.aspx
This URL should allow you to sign in and sign out automatically

With these TWO tests you will ensure that ADFS is configured correctly

As far as concern to ADFS proxy, you need to export same certificate on ADFS server to ADFS Proxy
For production you do require public SSL cert

As far as concern to HA, you can build TWO ADFS servers in NLB \ HLB configuration in production network and you can build TWO adfs proxy (Web application proxy in ADFS 3.0) in DMZ in NLB / HLB
Once environment setup you can test functionality by turning off one server at a time

Use SQL standard \ clustered database in production ADFS.
ADFS does support Windows Internal Database (WID), but it is recommended for lab only
If your user count is less, you can use WID without any problems
While setting up ADFS in production \ lab, you need to select virtual name such adfs.domain.com which should be resolvable from public DNS out on internet and differ from your actual server Hostname

U also do require Directory sync server for account synchronization to O365

Here are very good reading wrt to 2012 R2 ADFS and O365:
http://blogs.technet.com/b/askpfeplat/archive/2014/03/31/how-to-build-your-adfs-lab-part4-upgrading-to-server-2012-r2.aspx
http://blogs.catapultsystems.com/smcneill/archive/2014/01/04/setting-up-adfs-3-0-server-2012-r2-for-office-365.aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now