Commerce Server Blog

In my previous blog entry, I have explained how to create ASP.NET ecommerce website in CS2009.

http://microsoftblog.co.in/commerceserver/aspnet-website-in-commerce-server-2009/

Now, in this post, I will explain how to import CS2009 pub without using “SharePointCommerceServicesConfiguration” tool.

• Open Commerce server manager.
• Right click on commerce sites –> New –> Unpack site.
  
• Navigate to “\Program Files\Microsoft Commerce Server 2007\Microsoft Commerce Server 2009\Site” directory and click on “MicrosoftCommerceDefaultSiteWithSampleData.pup” file or “MicrosoftCommerceDefaultSiteNoData” file.
• Now site unpacker wizard starts and it will create commerce server 2009 sites.
• In the first screen, click on custom unpack.
• In the second screen, click on “Create a new site” radio button.
• In the third screen, give the site name as “SampleSite”.
• In the fourth screen, make sure you add all available resources to “resource to unpack” section.
• In the fifth screen, leave the default configuration (it creates new profile and CS authentication resources).
• In the sixth screen, all databases are shown, if required, you can change the database name or database location.
• In the seventh screen, make sure you select all applications.
• In Eight screen, the tool will show the website details. If you want to can change the virtual direction name, you can do it here.
• By clicking next, the site creation process starts. In between, the tool asks for profile system resources (schema, site terms, expression definitions) and schema definition scripts. Keep the defaults (don’t change them).
• After successfully creation of sites, the site packer shows the popup.

If you observe commerce server manager, web services are created but it will not create the site. So, we have to manually add our web application under application directory in commerce server manager.

Commerce server provides independent profile mechanism for authorization. Windows live Id is Microsoft Internet based software service that is designed to manage identity & trust within the Microsoft eco system. Let’s leverage the Windows Live ID as a login authentication method for an e-Commerce site. Using a username and password that the user is familiar with will reduce the costs and time spent on managing user identities. This article will describe the process of integrating Windows Live ID with the Commerce Server Starter Site.

Following are the steps in authentication process

1. User clicks on sign-in or sign-out button in starter site.
2. If user already signed in then
   1. Retrieve user’s unique identifier from stoken.
      1. If User has commerce server profile
         1. If yes, validate user and perform other login tasks.
         2. Starter site will display personalized contents to the user.
      2. If user doesn’t have commerce server profile
         1. Redirect the user to registration page.
         2. User fills the registration form.
         3. Create user profile and other login tasks.
         4. Starter site will display personalized contents to the user.
3. If user hasn’t signed in then
   1. Redirect user to windows live ID.
   2. Windows live ID authentication process will happen.
   3. Redirect to starter site. 

This is two step process.

1. Register your application with windows live.
2. Change your web site to use windows live ID.

Click on below URL to register your application with windows live
https://msm.live.com/app/

The second step is to do following changes in starter site so that the application asks windows ID authentication instead of default profile authentication. Here are the steps.

• Copy WindowsLiveLogin.cs (from the Web Authentication SDK, downloaded above) to the Starter Site’s App_Code directory. You can download web authentication SDK from below link
  http://www.microsoft.com/downloads/details.aspx?FamilyId=24195B4E-6335-4844-A71D-7D395D20E67B&displaylang=en
• Create a new login page say LiveIDLoginPage.aspx
• Create a new registration page say LiveIDRegistrationPage.aspx.
• Update the Starter Site’s web.config file to reference the new pages – e.g. loginUrl=“~//LiveIDLoginPage.aspx”
• Add the following <appSettings> section to the web.config file. Make sure you set your application values appropriately.
  <appSettings>
  <add key=”wll_appid” value=”123456789″/>
  <add key=”wll_secret” value=”MySecretKeyForStarterSite”/>
  <add key=”wll_securityalgorithm” value=”XXXXX”/>
  </appSettings>
• In your LiveIDLoginPage.aspx page, verify if the user has already been authenticated by Windows Live ID. If not, redirect to Windows Live ID sign-in page.
• Retrieve user’s unique identifier and verify if profile exists in Commerce Server. Redirect to new user registration page if needed

This article will help you to understand how to implement window Live Id authentication and doesn’t provide end to end code? Many companies doesn’t want the user profile created at different entity (like passport authentication). Here we are using windows live ID only for authentication and rest of the user details are captured during registration process. This will help us to perform targeting our site content appropriately.