Demonstrating IdP Discovery using Common Domain Cookie 5.3 Note: Features related to Common Domain Cookie is not being actively maintained, neither in the codebase or this documentation. Since NemLog-in does not use Common Domain Cookie, it’s highly unlikely you would use this feature. This section illustrates how to perform IdP Discovery as describe in the SAML Identity Provider Discovery Profile by enabling the Common Domain Cookie approach in the Federation. Note that IdP Discovery is only relevant when multiple IdPs are present in the same federation. The setup explained in this section corresponds to the configuration illustrated in the first figure in chapter 11, which consists of two Service Providers and two Identity Providers. It is assumed that the certificates are already installed as explained in section 5.1. 5.3.1 Preparation Create the directory ”C:\inetpub\cdctest”. Copy the and “dk.nita.saml20\WebsiteDemo” directories to the “dk.nita.saml20\IdentityProviderDemo” “C:\inetpub\cdctest” directory. Rename the folder to and the folder to “WebsiteDemo” “sp1” “IdentityProviderDemo” “idp”. Make a copy of the folder and name the new copy “sp1” “sp2”. Open the IIS Manager and add three new Sites: One that points to Service Provider 1, the directory. demosp1 sp1 One named that points to Service Provider 2, the directory. demosp2 sp2 And finally one named pointing to the Identity Provider, the directory. demoidp idp In the IIS Manager edit the bindings for the three sites: For Service Provider 1: Add the entries: demosp1.commondomain.local demosp1.local For Service Provider 2: Add the entries: demosp2.local Identity Provider: Add the entry: commondomain.local (Note that the Identity Provider must be located on the domain corresponding to the common domain. This is not a requirement for Identity Providers in general, but is the only way to make it work with the Demo IdP. 7. Add the following entries to the hosts file (C:\Windows\System32\drivers\etc\hosts): 127.0.0.1 127.0.0.1
5.3 Demonstrating IdP Discovery using Common Domain Cookie Note: Features related to Common Domain Cookie is not being actively maintained, neither in the codebase or this documentation. Since NemLog-in does not use Common Domain Cookie, it’s highly unlikely you would use this feature. This section illustrates how to perform IdP Discovery as describe in the SAML Identity Provider Discovery Profile by enabling the Common Domain Cookie approach in the Federation. Note that IdP Discovery is only relevant when multiple IdPs are present in the same federation. The setup explained in this section corresponds to the configuration illustrated in the first figure in chapter 11, which consists of two Service Providers and two Identity Providers. It is assumed that the certificates are already installed as explained in section 5.1. 5.3.1 Preparation Create the directory ”C:\inetpub\cdctest”. Copy the “dk.nita.saml20\WebsiteDemo” and “dk.nita.saml20\IdentityProviderDemo” directories to the “C:\inetpub\cdctest” directory. Rename the “WebsiteDemo” folder to “sp1” and the “IdentityProviderDemo” folder to “idp”. Make a copy of the “sp1” folder and name the new copy “sp2”. Open the IIS Manager and add three new Sites: One demosp1 that points to Service Provider 1, the sp1 directory. One named demosp2 that points to Service Provider 2, the sp2 directory. And finally one named demoidp pointing to the Identity Provider, the idp directory. In the IIS Manager edit the bindings for the three sites: For Service Provider 1: Add the entries: demosp1.commondomain.local demosp1.local For Service Provider 2: Add the entries: demosp2.local Identity Provider: Add the entry: commondomain.local (Note that the Identity Provider must be located on the domain corresponding to the common domain. This is not a requirement for Identity Providers in general, but is the only way to make it work with the Demo IdP. 7. Add the following entries to the hosts file (C:\Windows\System32\drivers\etc\hosts): 127.0.0.1 127.0.0.1
Net%20SAML2%20Service%20Provider%20Framework.docx