Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 184 Source: ADFS2.0

A token request was received for a relying party identified by the key 'urn:federation:MicrosoftOnline', but the request could not be fulfilled because the key does not identify any known relying party trust.
Key: urn:federation:MicrosoftOnline

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.
According to Microsoft, this may be caused by the fact that the Uniform Resource Identifier (URI) that identifies the relying party trust does not exist. Review the key data, which is the URI that is specified for the relying party trust. If the URI appears to be valid and trustworthy, verify that it is configured for the relying party in the AD FS 2.0 snap-in. You can manage the URI on the Identifiers tab in the relying party trust properties.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.