Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Issue adding relying party - An error occured during and attempt to read the federation metadata

$
0
0

Hi,

I followed this guide to set up an ADFS 2.0 lab environment. The only difference that I have is that I did not set up the ADFS server and the WIF application to be on the same box but rather on 2 different.

My server configuration is as follows:

  • Server 1 - win 2008 R2 - Domain Controller, DNS
  • Server 2 - win 2008 R2 - CA, ADFS
  • PC 3 - win 7 - Development environment

I successfully created my ADFS configuration STS and could add that as a STS reference in the .Net application in Visual Studio 2008 on my dev environment. I then needed to configure the WIF application to be a valid Trusted Relying Party and followed these steps:

  1. Created an SSL certificate request
  2. Submitted an SSL request and issued it via the CA
  3. Installed it on the Development environment
  4. Ran the ADFS 2.0 'Add Relying Party Trust Wizard'
  5. Got stuck with trying to find the Federation metadata address of the dev environment

No matter what URL I put in https://win7dev.mydomain.com/ClaimsAwareWebAppWithManagedSTS (is what it is on my dev environment IIS), I just cannot seem to get this going.

 

I can run my app now from the ADFS box by connection to https://win7dev.mydomain.com/ClaimsAwareWebAppWithManagedSTS but that url would just not work when adding as a trusted relying party :(

 

Could a certificate mismatch error be the problem?

Thanks

Mike

 


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>