ADFS 3.0 and Azure
I have installed a load balancing set of VM's both ADFS 3.0 and Web Proxy in the Azure cloud. I have an existing virtual VPN gateway back to my infrastructure running. Everything runs fine and I can hit the metadata.xml file from any browser internally and externally. When I try to add the metadata.xml file to third-party applications they error out about authentication or error opening connection. I figure if I can hit the metadata.xml file from a browser these applications should hit them. Any suggestions? Thanks
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
First off, the 3rd party apps should reach your AD FS server's metadata URL e.g. https://adfs1.contoso.com/federationmetadata/2007-06/federationmetadata.xml btu failed as it is not established with relying party trust yet. See MS test lab use case
Probably is to follow on to "Create a relying party trust on your federation server" and checking a valid SSL certificate in the computer certificate store for third party certificate should contain the name of their web server, and in the example above it (claimapps - "3rd party") has SSL cert CN map and bind to webserv1.contoso.com.
5. To configure claimapp to work with your federation server, do the following:https://technet.microsoft.com/en-us/library/dn280939.aspx
Run FedUtil.exe, which is located in C:\Program Files (x86)\Windows Identity Foundation SDK\v3.5.
Set the application configuration location to C:\inetput\claimapp\web.config and set the application URI to the URL for your site, https://webserv1.contoso.com /claimapp/. Click Next.
Select Use an existing STS and browse to your AD FS server's metadata URL https://adfs1.contoso.com/federationmetadata/2007-06/federationmetadata.xml. Click Next.
Select Disable certificate chain validation, and then click Next.
Select No encryption, and then click Next. On the Offered claims page, click Next.
Select the check box next to Schedule a task to perform daily WS-Federation metadata updates. Click Finish.
Your sample application is now configured. If you test the application URL https://webserv1.contoso.com/claimapp, it should redirect you to your federation server. The federation server should display an error page because you have not yet configured the relying party trust. In other words, you have not secured this test application by AD FS.
You must now secure your sample application that runs on your web server with AD FS. You can do this by adding a relying party trust on your federation server (ADFS1).
Probably is to follow on to "Create a relying party trust on your federation server" and checking a valid SSL certificate in the computer certificate store for third party certificate should contain the name of their web server, and in the example above it (claimapps - "3rd party") has SSL cert CN map and bind to webserv1.contoso.com.
Are you saying download their SSL cert from the third-party vendor and add it to Third Party Root Cert Auth?
Update on Error
details = Unable to register idp
Error in registering Idp for account id
Error in parasing Idp metadata form url "https://<adfs-server>/federationm
Exception: peer not authenticated
details = Unable to register idp
Error in registering Idp for account id
Error in parasing Idp metadata form url "https://<adfs-server>/federationm
Exception: peer not authenticated
Trying to get your picture of setup...
I meant trust relationship must be established btw ADFS as the Identity server, Azure ACS as federation broker. Hence Federation metadata address of Azure need to be used and added as trusted relying party. Likewise Azure ACS need the Federation metadata address of ADFS.
Azure ACS - e.g. https://[namespace].accesscontrol.
ADFS - e.g. https://[server name].cloudapp.net/Federat
Ref - http://www.ben-morris.com/set-up-a-federated-identity-provider-on-azure-using-active-directory-and-adfs-2-0/
Thereafter you need to create claim rules e.g. configured the ADFS server to send the correct claims we have to ensure that Azure ACS passes them through to any application.
Then the Apps (assume web app) can use federated login by be registering as a relying party application in Azure. And to link the Apps up to Azure ACS you will need the management key from your ACS instance. This can be collected from the Azure ACS Management Portal. The Apps is linked up to Azure ACS using that management key from your ACS instance. Thereafter the Apps will has its config file (like web.config) configured...
Just to understand the setup as I may miss out your use case...
I meant trust relationship must be established btw ADFS as the Identity server, Azure ACS as federation broker. Hence Federation metadata address of Azure need to be used and added as trusted relying party. Likewise Azure ACS need the Federation metadata address of ADFS.
Azure ACS - e.g. https://[namespace].accesscontrol.
ADFS - e.g. https://[server name].cloudapp.net/Federat
Ref - http://www.ben-morris.com/set-up-a-federated-identity-provider-on-azure-using-active-directory-and-adfs-2-0/
Thereafter you need to create claim rules e.g. configured the ADFS server to send the correct claims we have to ensure that Azure ACS passes them through to any application.
Then the Apps (assume web app) can use federated login by be registering as a relying party application in Azure. And to link the Apps up to Azure ACS you will need the management key from your ACS instance. This can be collected from the Azure ACS Management Portal. The Apps is linked up to Azure ACS using that management key from your ACS instance. Thereafter the Apps will has its config file (like web.config) configured...
Just to understand the setup as I may miss out your use case...
Premium Content
You need an Expert Office subscription to comment.Start Free Trial