Using OAuth 2.0 for authorizing client application access to Hybrid Data Pipeline data sources
- Last Updated: April 11, 2025
- 2 minute read
- Hybrid Data Pipeline
- Version 4.6
- Documentation
Using OAuth 2.0 for authorizing client application access to Hybrid Data Pipeline data sources
Hybrid Data Pipeline supports OAuth 2.0 for authorizing client application access to OData-enabled data sources. Authorization Code and Password grant types are supported. In an OAuth 2.0 implementation, the Hybrid Data Pipeline server functions as the Authorization Server as well as the Resource Server. In its role as the Authorization Server, Hybrid Data Pipeline returns an access token to the client application to grant the client application access to a data source.
Only OData-enabled data sources may be authorized using OAuth 2.0. Therefore, the client application must be able to consume data from an OData endpoint. The client application must also be configured to manage OAuth values and tokens as required by the grant type. Note that third-party applications, such as Power BI, often require additional configuration to access Hybrid Data Pipeline resources.
The following steps must be taken to implement OAuth 2.0 for client application access. See the corresponding topics for more information.
- Create an OData-enabled Hybrid Data Pipeline data source. This step provides you with an OData endpoint which can be authorized for client application access.
- Register the client application with the Hybrid Data Pipeline server. The registration of a client application returns a client ID and client secret which can then be used to obtain access and refresh tokens.
- Configure the client application to access the Hybrid Data Pipeline data source. The client application must be configured for the grant type you are using.
See also Configuring Postman as a third-party client application for OAuth 2.0.