This project is read-only.

This Toolkit is now deprecated and is now

superseded by Windows Azure Mobile Services

During the early previews of Windows 8, the Windows Azure Toolkit for Windows 8 provided developers with the first support for building backend services for Windows Store apps using Windows Azure.  The main areas of feedback we received from mobile developers was that they wanted a turn-key set of services for common functionality such as notifications, auth, and data.   Windows Azure Mobile Services directly reflects this feedback by enabling developers to simply provision, configure, and consume scalable backend services. The downloads for this toolkit will be removed on the week of Feb 1st 2013.  Future improvements will be channeled into Windows Azure Mobile Services rather than this toolkit. 

To get started with Mobile Services, sign up for a Windows Azure account and receive 10 free Mobile Services.


How to Deploy the Margie’s Travel Sample to Windows Azure

The following section will guide you through the process of configuring and deploying the Margie’s Travel sample to Windows Azure.

Configuring Access Control namespace

  1. Create an ACS namespace; please refer to the walkthrough here.
  2. Create the identity providers you want to support from the Identity providers item on the left menu.

    image

  3. Create a new relying party for the Margie’s Travel portal by providing your Windows Azure hosted service account information as depicted below. Make sure that the Token Format is set to SWT.

  4. Select which identity providers you want to support.

  5. Generate a signing key.

  6. Now, create a new relying party for the bouncer service making sure that you also set the Token Format as SWT.

  7. Select the list of identity providers you want to support.

  8. In the Token Signing Settings section, provide the same key generated for the Margie’s Travel portal relying party instead of generating a new one.

    

  9. On the left menu, click the Rule groups item and go to the rule associated for both relying parties on the right panel.

    image

  10. On the Edit Rule Group page, click Generate.

    image

  11. Select all the identity providers from the list and click Generate.

    image

Configuring the Margie’s Travel Portal

  1. Open the MargiesTravel.sln solution in Visual Studio.

  2. Open the Web.Config file located in MargiesTravel.Web project.
  3. Locate the audienceUris section and replace the local Uris by the ones you created in ACS.

  4. Locate the wsFederation section and replace the issuer and realm values: 

  5. Locate the certificateReference section and replace the Windows Azure DevFabric thumbprint with the one associated with your hosted service:

    Note: You must have uploaded an SSL certificate to Windows Azure portal.

  6. Locate the trustedIssuers section and provide your hosted service URL as the name and the token signing key for the thumbprint attribute:

  7. Open the ServiceConfiguration.Local.cscfg file inside the MargiesTravel.Cloud project and replace the local storage account information for you Windows Azure storage account and replace the WNS information with the values provided by the Windows Push Notifications & Live Connect portal:

    Note: You can grab your Windows Push Notifications & Live Connect information from https://manage.dev.live.com/build.

  8. Replace the thumbprint on the Certificate node by the one associated with your hosted service:

  9. Open the NotificationService.cs file located into the App_Data folder on the MargiesTravel.Web project and provide the connection string for your Windows Azure storage account:

  10. Open the Index.cshtml located inside the Views/MyTrips folder and provide replace the values as depicted below:

  11. Deploy the project to Windows Azure

 

Configuring Margie’s Travel Client

  1. Open the MargiesTravel.Client solution

  2. Open the security.js file inside the js folder and replace the following variables with you hosted service and ACS configuration as depicted below:

  3. Open the common.js file inside the js folder and replace the local Url with your hosted service Url:

Last edited Jan 21, 2013 at 9:00 PM by nharris, version 7

Comments

No comments yet.