index > Claims based access platform (CBA), code-named Geneva > MSIS7007: The requested relying party 'https://localhost/ClaimsEnableWebSite/' is unspecified or unsupported. If a relying party was specified, it is possible that you do not have permission to access the relying party. Contact your administrator for det

MSIS7007: The requested relying party 'https://localhost/ClaimsEnableWebSite/' is unspecified or unsupported. If a relying party was specified, it is possible that you do not have permission to access the relying party. Contact your administrator for det

In the Identity Developer's training kit - Hands on lab "Web Site and Identities" Task 1 -Referencing an STS Published by an Instance of Geneva Server, I get this error

"MSIS7007: The requested relying party 'https://localhost/ClaimsEnableWebSite/' is unspecified or unsupported. If a relying party was specified, it is possible that you do not have permission to access the relying party. Contact your administrator for details. "

Did any one else face this? I have followed the steps provided in the lab and did not do any changes/modifications.

Is this related to any configuration settings that I may need to alter

Gaurab Bhattacharjee

Hi Gaurab,
see http://social.msdn.microsoft.com/Forums/en-US/Geneva/thread/c41f65bf-952c-4141-b96f-c469f5a25dac. We are in the middle of some interop tests on that server, and in the meanwhile the online ADSF2.0 (geneva server) endpoint for the training kit will be unavailable. We will restore it in a couple of weeks. Apologies for the setback! As a mitigation, the steps you'd do from the development perspective are exactly the same you do in the other exercises involving local STSes: hence from the learning perspective you don't really miss anything :)

HTH

Vittorio

Marked As Answer byGaurab Bhattacharjee Tuesday, September 01, 2009 11:42 AM

Vittorio Bertocci - MSFT

The error message above is usually logged when the relying party cannot be found in the Geneva Server database. It could be a typo in your case, i.e. 'https://localhost/ClaimsEnabledWebSite'.

Stefan Miltchev - MSFT

Thanks for responding Stefan. When I worked on the same project today it worked, without any changes (not even to the URL) and I was able to navigate to https://localhost/ClaimsEnableWebSiteEx01/SecretPage.aspx.

So I am trying to understand if this was a problem with the Geneva Server [which for this particular lab in the training is external]? If yes what caused it and how it got fixed without any changes?

Let me know if you have any pointers/possibilities.

Gaurab Bhattacharjee

Marked As Answer byGaurab Bhattacharjee Tuesday, September 01, 2009 11:42 AM

Vittorio Bertocci - MSFT

You can use google to search for other answers

Custom Search

More Threads

• Same cards at same time from two different PCs.

• Error creating a ASP.NET Security Token Service Web Site

• Create new STS in current solution is failing

• Circular redicrect and case sensitive uris

• Geneva Server with IAG & MOSS

• Securely signing out (and staying signed out)

• Where can I download Beta 1?

• Problem with Core Vista Audio

• Visual Studio 2008 student edition and express edition compatibility

• SOLVED: Web services federation with Geneva Server Beta 2