Authenticating users in Retail online sample stores

아티클
05/18/2015

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3

The Microsoft Dynamics AX 2012 for Retail online sample stores authenticate customers and site administrators by using the two authentication types supported by Microsoft SharePoint Server 2013:

Forms-based authentication for customers.
Windows classic mode authentication for site administrators.

For more information about Windows and forms-based authentication with SharePoint Server 2013, see Authentication overview for SharePoint 2013 and Authentication, authorization, and security in SharePoint 2013.

Configuration and authentication

Site administrators configure how site users are authenticated by specifying publishing portal settings in PowerShell deployment scripts. For more information, see Install a Retail online store (e-commerce). The PowerShell deployment scripts create web applications in Internet Information Services (IIS) and SharePoint. For example, the deployment scripts can create the following two web applications for the Contoso sample online store:

For SharePoint, the web application is called Out of box Store front – Public 1.
For IIS, the web application is called RetailC2WebApplication-1.

The deployment scripts also create site collections on the SharePoint web application. The default settings for the site collections configure port 40003 for site administrators and port 40002 for customers. For example, the Contoso online sample store can authenticate users who access the site URLs as shown in the following table.

URL	Authentication method
http:// computername:40003/sites/RetailPublishingPortal	Windows authentication. When you sign in your current Windows user ID is used for authentication.
http:// computername:40002/sites/RetailPublishingPortal	Forms-based authentication that includes external logon providers such as Facebook. Users may remain anonymous if they decide not to log on.

Authenticating customers by using forms-based authentication

The Retail online sample stores use three types of authentication for store customers. Customers can remain anonymous, create a new user ID, or log on as a returning user. Anonymous users may purchase products, but their identifying information and credentials are not stored permanently. When a customer creates a new user ID, a customer record is created in the CustTable table in AX 2012. Credentials for returning customers are validated by using forms-based authentication.

When you install and deploy the sample sites, you configure the default validation for customers’ credentials. You can configure the SharePoint database as the membership and role provider or you can configure Facebook as an external logon provider. The Dynamics custom claims provider implements the mapping of a customer in the AX 2012 database to a customer of the Retail online sample store.

Authentication process

The following diagram illustrates the components and databases involved in authenticating a user who signs in to the Contoso site on port 40002.

Authentication process flow in Retail online store

The following numbered steps describe the processes in the diagram.

The user clicks Sign In on the store home page or accesses a page that requires authentication.
The user is redirected to the Login.aspx page.
The user enters an e-mail address and password. Data is sent to the SharePoint Secure Token Service (STS). The STS calls the forms-based identity provider, which is based on the ASP.NET forms-base authentication provider and the AX 2012 Retail custom claims provider.
The identity provider uses the forms-based membership database SpFBA to validate the user name and password.
The STS may invoke other identity providers, such as Facebook.
After authentication, the Dynamics custom claims provider queries the customer mapping database SpSQLAuthZ, returns the AX 2012 customer ID for the user, and adds it to the claim set.
The STS returns the claim set back to the page.
The page is sent to the user’s browser.

Authenticating a new customer

A new customer who does not decide to register an account receives a temporary token that SharePoint uses to authenticate the session. The new customer can check out as a guest or click Register a New Account on the Sign In page to create a customer record in the AX 2012 database. Registering a new account sets up the user as a customer in the AX 2012 database and creates a mapping between the customer’s credentials and the record for the customer in AX 2012.

Authenticating a returning customer

After a returning customer is authenticated, the custom claims provider adds the customer information from the AX 2012 database to the claim.

Extending user authentication by adding a logon provider

You can configure Facebook as an external logon provider when you install the Retail online store. Source code for integrating Facebook authentication is provided in the Retail SDK as an example for extending user authentication. To find the sample code, open the file Retail SDK\Online Channel\Storefront.sln in Visual Studio. The source code for Facebook integration is found in the SharePoint.Web.Common project under the Facebook folder.

다음을 통해 공유