This topic applies to Dynamics 365 for Retail, Dynamics 365 for Finance and Operations, Enterprise edition, and Dynamics 365 for Operations.
This topic provides an overview of the process for configuring a new OpenID authentication provider.
The E-Commerce platform uses industry-standard OpenID Connect as the mechanism for authentication. This article covers the pages that you use to register the OpenID providers that are used in an online store. Retail Server uses OpenID Connect as the mechanism to support authenticated customers. OpenID Connect is a universally accepted standard that acts as simple and evolved identity provider on top of OAuth 2.0. Retail Server can be integrated with both ready-to-use OpenID providers through the Microsoft Azure Access Control service and other independently available providers. In addition, any custom providers that support OpenID connect can be integrated and registered.The following illustration shows the step-by-step handshake that occurs between the Retail Server and the E-Commerce front-end server to pass the authentication token for subsequent calls.
Here is a walkthrough of the process for registering OpenID providers so that they can be used in Retail Server.
- From the Retail IT workspace, go to Retail shared parameters > OpenID providers. You can use the OpenID providers page to register additional providers. For every provider that you support, enter the details of the OpenID provider and the details of the relying parties. Retail Server uses this information to request and use an authentication token for subsequent calls.
- Run distribution schedule 1110.
For the test online store, edit the web.config file so that it specifies the correct redirect URL and domain, as shown in the following example. If you're using a third-party online store, this information can be stored as required.