Difference between revisions of "ADFS Implementation"
| Line 1: | Line 1: | ||
[http://www.microsoft.com/windowsserver2008/en/us/ad-fs-2-overview.aspx ADFS 2.0] is Microsoft's Windows Server component that enables Single Sign On. It includes sufficient support for the SAML standards so as to be compatible with GFIPM. The contents of this article are not comprehensive for deploying ADFS 2.0 as a GFIPM Identity Provider, but it does cover a few of the areas where conforming to the [http://it.ojp.gov/docdownloader.aspx?ddid=1336 GFIPM Web Browser User-to-System Profile] varies from ADFS 2.0's defaults. | [http://www.microsoft.com/windowsserver2008/en/us/ad-fs-2-overview.aspx ADFS 2.0] is Microsoft's Windows Server component that enables Single Sign On. It includes sufficient support for the SAML standards so as to be compatible with GFIPM. The contents of this article are not comprehensive for deploying ADFS 2.0 as a GFIPM Identity Provider, but it does cover a few of the areas where conforming to the [http://it.ojp.gov/docdownloader.aspx?ddid=1336 GFIPM Web Browser User-to-System Profile] varies from ADFS 2.0's defaults. | ||
| + | |||
| + | == Federation Terminology == | ||
| + | |||
| + | The terminology used by Microsoft varies from the terminology used within GFIPM standards. You may want to familiarize yourself with [http://technet.microsoft.com/en-us/library/adfs2-help-terminology%28WS.10%29.aspx ADFS Terminology] and [http://it.ojp.gov/docdownloader.aspx?ddid=1333 GFIPM Terminology] before you proceed. The two biggest terminology things to be aware of is that within ADFS what it calls *claims* are termed *attributes* within GFIPM, and ADFS's *Relying Parties* are GFIPM *Service Providers*. There are many other variations as well, but these two are fundamental in recognizing. | ||
| + | |||
| + | == Attribute Names == | ||
| + | |||
| + | It is important ... | ||
Revision as of 19:08, 1 February 2011
ADFS 2.0 is Microsoft's Windows Server component that enables Single Sign On. It includes sufficient support for the SAML standards so as to be compatible with GFIPM. The contents of this article are not comprehensive for deploying ADFS 2.0 as a GFIPM Identity Provider, but it does cover a few of the areas where conforming to the GFIPM Web Browser User-to-System Profile varies from ADFS 2.0's defaults.
Federation Terminology
The terminology used by Microsoft varies from the terminology used within GFIPM standards. You may want to familiarize yourself with ADFS Terminology and GFIPM Terminology before you proceed. The two biggest terminology things to be aware of is that within ADFS what it calls *claims* are termed *attributes* within GFIPM, and ADFS's *Relying Parties* are GFIPM *Service Providers*. There are many other variations as well, but these two are fundamental in recognizing.
Attribute Names
It is important ...
