CodeFrenzy

I know this is not rocket science but it’s actually something I’d never had to do until recently. Normally I populate my drop down lists (and repeaters, etc etc) using data from databases, not XML.

However, fear not. Using XML as a datasource in .NET is super easy. Here is one way to do it:

1
2
3
4
5
6
7
8

XmlDataSource source = new XmlDataSource();
source.DataFile = Server.MapPath("Values.xml");
source.XPath = "ParentElement/ValueList/ValueItem";
 
myDropDownList.DataSource = source;
myDropDownList.DataTextField = "Text";
myDropDownList.DataValueField = "Value";
myDropDownList.DataBind();

And your xml file, Values.xml, may look something like:

<?xml version="1.0" encoding="utf-8"  standalone="yes" ?>
<ParentElement>
  <ValueList>
    <ValueItem Text="Item 1" Value="1" />
    <ValueItem Text="Item 2" Value="2" />
  </ValueList>
</ParentElement>

Happy coding!

The following article is part 4 and therefore the last in a 4 part series of articles about developing .NET applications using SSL. Part 1 in this series can be found here, part 2 can be found here and part 3 can be found here.

How to set up a web application to automatically redirect to HTTPS if accessed via HTTP when SSL is required

SSL can be “required” at the site level, folder level or even file level.

If any file that has SSL set to “required” is requested via HTTP, HTTP Error 403;4 “Forbidden” will be returned automatically by IIS.  As far as I can tell, there is no simply way to tell IIS to re-direct to the same page via HTTPS.  This effect can be achieved in two different ways and if “defence in depth” is the preferred approach then both solutions can be implemented together.  Note that both solutions require custom code to be written however.

Redirect with IIS and code:

1. Create a new Web Form (aspx) in your Web Application called RedirectToSSL (or similar).
2. In the Page_Load event handler, insert the following code:
   
   
   ^?View Code CSHARP

   1 2 3 4 5 6 7 8

   string redirectUrl = HttpContext.Current.Request.Url.Query; redirectUrl = redirectUrl.Substring((redirectUrl.LastIndexOf(';')+1) , redirectUrl.Length - (redirectUrl.LastIndexOf(';')+1));   System.UriBuilder secureUrlBuilder = new System.UriBuilder(redirectUrl); secureUrlBuilder.Scheme = System.Uri.UriSchemeHttps; secureUrlBuilder.Port = -1; // Use default port HttpContext.Current.Response.Redirect(secureUrlBuilder.Uri.ToString(), true);

3. The aspx needs to be at least 512 bytes, otherwise IIS won’t redirect to it. So make sure you don’t delete everything out of it, it should never get displayed anyway.
4. In IIS, right-click your Web Site and go to Properties > Custom Errors.
5. Select the “403;4” HTTP error in the list HTTP errors and click the Edit Properties button.
6. Select “URL” from the Message type drop-down list and enter “/RedirectToSSL.aspx” into the URL textbox, as shown below.
7. Press OK twice to close the dialogs down.
8. Restart the website and/or reset IIS to ensure all settings have been applied.
9. Open Internet Explorer and go to: https://<servername>/<securedpage> and verify that you are automatically redirected to the https version of the same page.

1. Insert the following code at the beginning of the Page_Load event handler of every page that needs to be secured:
   
   
   ^?View Code CSHARP

   1 2 3 4 5 6 7 8 9

   // Make sure the request has come through SSL (ie that HTTPS has been used) if (!HttpContext.Current.Request.IsSecureConnection) { System.Uri currentUrl = HttpContext.Current.Request.Url; System.UriBuilder secureUrlBuilder = new System.UriBuilder(currentUrl);   secureUrlBuilder.Scheme = System.Uri.UriSchemeHttps; secureUrlBuilder.Port = -1; HttpContext.Current.Response.Redirect(secureUrlBuilder.Uri.ToString(), true); }




• 

The following article is part 3 in a 4 part series of articles about developing .NET applications using SSL. Part 1 in this series can be found here and part 2 can be found here.

Installing Certificates into the correct Certificate Stores

Applications depend heavily on server SSL and client certificates being installed in the correct certificate stores. Certificates may need to be copied and pasted or exported and imported into stores in order to get the systems correctly working together in a secure manner.

Client application (with client certificate):

1. Local Computer > Trusted Root Authority store should contain the Root CA certificate of the Server SSL Certificate Issuer of the Web application.
2. Current User > Personal store should contain the Client Certificate for the Client application.
3. Current User > Trusted Root Authority store should contain the Root CA certificate of the Client Certificate Issuer of the Client application

1. Local Computer > Personal store should contain the Server SSL Certificate for the Web application.
2. Local Computer > Trusted Root Authority store should contain the Root CA certificate of the Server SSL Certificate Issuer of the Web application.
3. Local Computer > Trusted Root Authority store should contain the Root CA certificate of the Client Certificate Issuer of the Client application.
4. Current User > Trusted Root Authority store should contain the Root CA certificate of the Client Certificate Issuer of the Client application.

1. From the Start menu, select Run, type “mmc” and click OK. This will open the Microsoft Management Console.
2. Click on the File menu option then on “Add/Remove Snap-in”.
3. In the Add/Remove Snap-in dialog, click the Add button.
4. From the Add Standalone Snap-in dialog, select “Certificates” from the list of snap-ins, and click Add.
5. Select the “Computer account” option and click Add. Select “Local computer” and click Finish.
6. If you are logged in as the user that will be used to run the client application, add the “My user account” as well.
7. Now you will be able to look through the Certificates that are installed in all the different stores.

The following article is part 2 in a 4 part series of articles about developing .NET applications using SSL. Part 1 in this series can be found here.

Setting Up Client Certificates

Client certificates can be used to authenticate the client connecting to a web application. The client can either be a browser or a custom written client application.

Requesting a client certificate:

1. Open IE (Firefox didn’t work so well for me…) and type in: http://<certauthservername>/certsrv/
2. Click on the “Request a certificate” link.
3. Click on the “Web Browser Certificate” link.
4. Enter all required information into the form shown above click “Submit”

1. Log onto the Windows Server 2003 machine and open the Certification Authority dialog from Administrative Tools.
2. Expand the root certification authority “Pending Requests” folder.
3. The certificate you just requested should be in the “Pending Requests” folder. Right-click on this request and select All Tasks > Issue. The certificate request will be removed from the “Pending Requests” folder and appear in the “Issued Certificates”.

1. Go back to IE on your web server and type in http://<certauthservername>/certsrv/ again.
2. Click on the “View the status of a pending certificate request” link.
3. Click on the certificate request you want to view.
4. Click on the “Install this certificate” link.
5. Click “Yes” on the dialog that opens to install the client certificate.
6. Click “Yes” on the next dialog as well.

1. On the client machine, open a Microsoft Management Console with the Certificates snap-in. Export the client certificate without the private key. This will generate a .cer file. Copy this file over to the server hosting the web application.
2. On the server hosting the web application, right-click the website in IIS and select “Properties”.
3. Under Properties, go to the “Directory Security” tab.
4. Under the Secure Communications section, click the “Edit” button.
5. In the Secure Communications dialog, change the “Client Certificates” option to “Require client certificates” and check the “Enable client certificate mapping” checkbox.
6. Click on the “Edit” button in the “Enable client certificate mapping” section.
7. This will open up the Account Mappings dialog.
8. Click the “Add” button.
9. Select the client certificate .cer file recently exported from the server that hosts the client application or client browser.
10. Give the mapping a relevant name and choose the windows user that the web application will be run under.
11. Click OK.
12. Click OK to close the Account Mappings dialog and Secure Communications dialogs.
13. Remove all other authentication options in the IIS manager Directory Security setting by clicking on the “Edit” button under Anonymous access and authentication control in the Directory Security tab.
14. Uncheck all authentication options and press OK.
15. Open up a browser and verify that you cannot reach the web site unless you navigate to it from the machine that has the client certificate installed on it.

The following article is part 1 in a 4 part series of articles about developing .NET applications using SSL. These articles are based on my experience and I hope that they will help others develop secure applications as well.

Setting up a Development or Test SSL Server Certificate on a Website in IIS (5.0/6.0)

When developing an application that requires SSL you may want a test SSL certificate to develop against.  You can request test SSL certificates from companies such as Verisign however these only last 14 days (and you will be called up by Versign representatives asking you when you would like to buy the real deal).  A much simpler and more flexible solution is to issue your own test SSL and client certificates by setting up a Windows Server 2003 machine that has the Certification Services windows component installed.

First, create an SSL server certificate request:

1. In IIS, right-click the Upload web site and select “Properties”.
2. Under Properties, go to the “Directory Security” tab.
3. Click the “Server Certificate” button and then click Next.
4. Select the “Create a new certificate” option and click Next.
5. Select the “Prepare the request now, but send it later” option and click Next.
6. Go through the next few forms and fill in all required information.
7. At the end of the wizard you will be asked to save the certificate request as a text file. Do this so you can send this request to a CA later.
8. You will be shown a summary of your SSL certificate request. Check this thoroughly to make sure you have all the correct values.
9. Click Next to finish the IIS Certificate Request Wizard.

1. Open IE (Firefox didn’t work so well for me…) and type in: http://<certauthservername>/certsrv/
2. Click on the “Request a certificate” link.
3. Click on the “advanced certificate request” link.
4. Click on the “Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file” link.
5. Copy and paste the contents of the certificate request generated by IIS (certreq.txt) into the “Saved Request” text box.
6. Click the “Submit” button to request the certificate

1. Log onto the Windows Server 2003 machine and open the Certification Authority dialog from Administrative Tools.
2. Expand the root certification authority “Pending Requests” folder.
3. The certificate you just requested should be in the “Pending Requests” folder. Right-click on this request and select All Tasks > Issue. The certificate request will be removed from the “Pending Requests” folder and appear in the “Issued Certificates”.

1. Go back to IE on your web server and type in http://<certauthservername>/certsrv/ again.
2. Click on the “View the status of a pending certificate request” link.
3. Click on the certificate request you want to view.
4. Click on the “Download certificate” link. A “File Download” dialog will open. Click Save to save the new SSL certificate as a .cer file.
5. Go back to the Web Site properties in IIS and from within the Directory Security tab, click on the Server Certificate button.
6. Select “Process the pending request and install the certificate” and click Next.
7. Browse to the certificate file saved to disk in step 4 above that contains the SSL certificate issued to this server by your test Certification Authority.
8. Follow the wizard until the SSL certificate has been successfully installed.

1. Once an SSL server certificate has been installed on the website, go back to IIS > > Properties > Directory Security tab > Secure Communications section and click on the “Edit” button.
2. Check the “Require secure channel (SSL)” checkbox but leave the “Require 128-bit encryption” checkbox empty.
3. Leave the “Client Certificates” section set to “Ignore client certificates” and the other two checkboxes unchecked for now.
4. Close this window down and restart the website and/or reset IIS.
5. Open up a browser and verify that you cannot reach the web site by using http only, instead you must use https.

1. If the browser tells you that your certificate was issued by an untrusted CA when you navigate to your website, you will have to download the CA certificate from your test Certification Authority website and install it into the Trusted Root Authority store of the Local Computer.
2. You may also find that the browser may tell you that the certificate is not valid because it was issued to a different name – that will happen if you are accessing your site using http://localhost/ rather than the server name. The certificate was most likely issued with the actual server name and the browser will think that your site is being spoofed if the domain name in the browser and the certificate don’t match. Use the server name instead.