I built a claims aware website in VS.2012 using the Identity and Access add-on.
The website is a templated vb.net website.
The Default page merely iterates any claims received after receiving an authorization token from STS.
I chose no encryption as instructed in the walkthrough.
I tested this application with the Local STS and it was able to authenticate and display the claims.
When we moved the application to our deployment Windows 2008 server and used another server with ADFS Management to configure it as a relying party the following happens.
1. When I try to access the Claims Aware website, it redirects to the ADFS trust server, and displays the templated login page.
2. I am able to use my network id and perform a valid login.
3. At that point, on the ADFS trust server an error is recorded in the event log:
Event ID 184:
A token request was received for a relying party identified by the key 'https://xxxx/yyyy/',
but the request could not be fulfilled because the key does not identify any known relying party trust.
Key: https://xxxx/yyyy/
This request failed.
User Action
If this key represents a URI for which a token should be issued, verify that its prefix matches the relying party trust that is configured in the
AD FS configuration database.
We have gone over the configuration again and again, both using the imported FederationMetadata.xml but also configuring it manually, and still cannot eliminate this error.
What else can we try to diagnose this error and fix it?
John Bailo RR Donnelley