Disclaimer: Use at your own risk – no warranties are granted or implied
If you’ve worked with Windows Identity Foundation (WIF) without the help of ADFS 2.0, you’ll run into situations where you’ll need to potentially generate or regenerate the metadata used for federation.
Additionally, while WIF supports SAML tokens, it doesn’t have support for SAML Passive Requestor protocol (urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST) - you get that with ADFS 2.0.
So, I needed the ability to quickly generate meta-data and regenerate as needed. I created a very simple tool – hacked in a few hours - that uses the meta data serialization support in WIF (MetadataSerializer) to generate the meta data.
So, this tool will generate the following metadata
Download
SAML IdP and SP
- IDPSSODescriptor "urn:oasis:names:tc:SAML:2.0:protocol"
- SPSSODescriptor "urn:oasis:names:tc:SAML:2.0:protocol"
And WS-Federation
- http://docs.oasis-open.org/wsfed/federation/200706
The tool makes use of the PropertyGrid for binding to some types used to generate, and in order to read the certificate private key it needs permissions – if you run elevated, you should have access.
Make sure, for today at least, you navigate to “Downloads” instead of using the quick link on the right side.
Summary
This document is a collection of items from public blog sites, Microsoft® internal discussion aliases (sanitized) and experiences from various Test Consultants in the Microsoft Services Labs. The idea is to provide quick reference points around various aspects of Microsoft Visual Studio® performance testing features that may not be covered in core documentation, or may not be easily understood. The different types of information cover:
How does this feature work under the covers?
How can I implement a workaround for this missing feature?
This is a known bug and here is a fix or workaround.
How do I troubleshoot issues I am having?
Visual Studio Performance Testing Quick Reference Guide