OAuth2 : 2-Legged

The Bazaarvoice Privacy API provides 2-legged and 3-legged methods for OAuth2 authentication. Use the 2-legged workflow if you want to authenticate your application without a Bazaarvoice Portal user involved in supplying credentials. Use the 3-legged workflow if you want to authenticate your application based on a Bazaarvoice Portal user supplying credentials. Due to its automation advantages, Bazaarvoice expects that the 2-legged workflow best fits the majority of client use cases for the Privacy API.

Introduction

The following tutorial explains how to use OAuth2 with the Bazaarvoice Privacy API using a two-legged workflow, which authenticates directly between the OAuth2 API and your Privacy application. If you wish that a Bazaarvoice Portal user supply credentials to complete the authentication process, refer to the 3-legged OAuth2 workflow .

❗️
Privacy requests made with OAuth2 client credentials (2-legged) would not include Social Commerce client's content.

Bazaarvoice has implemented 2-legged OAuth2, an open standard for access delegation. This style of OAuth is referred to as “2-legged” because it consists of two roles:

The Client Application : This is an application that would like to access data or interact with a Bazaarvoice service.
The OAuth2 API: A Bazaarvoice service that implements the OAuth2 standard and intermediates with the Client Application.

2-legged OAuth2 offers certain advantages including:

● Authentication is handled server to client and does not require an end user to manually supply credentials.
● As a well-known open standard, OAuth2 is easier to implement than a custom solution.

Resources

Refer to these resources for more information on OAuth2:

Introduction

❗️Privacy requests made with OAuth2 client credentials (2-legged) would not include Social Commerce client's content.

Resources

❗️
Privacy requests made with OAuth2 client credentials (2-legged) would not include Social Commerce client's content.