asp.net - FederationMetadata.xml Publish Process -


We are updating an ASP.NET web site project that has a click for "publish a web site" deployment The process uses ADFS 2.0 authentication to use. We currently have three different federation matadata.exml files for each environment (dev, test, prod). How do we publish these files in each environment?

We use the web configuration conversion file for the web.config file. But I do not believe it can be used for XML files? What I have done from those searches, I have found two potential responses, it does not look great, firstly a federation matadata file is removed and ADFS 2.0 (for manually configuring). We can do this but it seems that one step is on the back side, creating a dummy federation file in the second, and adding it to the global .asax.cs file. (). This approach is very laughing and hardly recommended approach.

Is there a recommended approach to this? Is anything clear that I am not seeing? Any thoughts on this will be highly appreciated!

If you actually manage to correct web.config, then you generate metadata on the fly (As requested). There is no need for the same code stable file for all the environment
Only in the telegram style for class names: ASP.NET application for a form It will be a HTTP handler (a controller for MVC). In Handler, you have to create an ApplicationServiceDescriptor, and you should use Metadatacierializer to spit XML. Fill it with information from FederatedAuthentication.WSFederationAuthenticationModule (which has been derived from web.config).


Comments

Popular posts from this blog

java - Can't add JTree to JPanel of a JInternalFrame -

javascript - data.match(var) not working it seems -

javascript - How can I pause a jQuery .each() loop, while waiting for user input? -