OData

The OData connector is a Palantir-provided driver for OData.

To create a new OData source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for OData-specific configuration and networking. For the complete property reference, see the official OData driver documentation ↗.

Configuration

The properties below are mandatory or recommended.

PropertyRequired?DescriptionDefault
AuthSchemeMandatoryThe scheme used for authentication. Accepted entries are NTLM, BASIC, DIGEST, NONE, NEGOTIATE, or SHAREPOINTONLINE.None
URLMandatoryThe root URL of the OData services file, also called the service root URL. For example, http://services.odata.org/V4/Northwind/Northwind.svc.https://{serverAddress}
InitiateOAuthRecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.REFRESH
OAuthClientIdRecommendedSpecifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server.
OAuthClientSecretRecommendedSpecifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server.

Networking

The table below lists the domains that the source needs to be able to access in order to successfully run.

For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

DomainRequired
<URL>Always. URL connection property
<FeedURL>FeedURL connection property
login.microsoftonline.comIf AuthScheme=AzureAD OR SharePointOnline AND SharePointUseSSO=FALSE
<SharePointSSODomain>If SharePointUseSSO=TRUE AND AuthScheme=SharePointOnline AND Domain of User is different than domain for SSO service
<KerberosKDC>:88If AuthScheme=Negotiate
<KerberosServiceKDC>:88If AuthScheme=Negotiate and Kerberos topology uses multiple realms
<OAuthAuthorizationURL>If AuthScheme=OAuth
<OAuthAccessTokenURL>If AuthScheme=OAuth
<OAuthRefreshTokenURL>If AuthScheme=OAuth
<OAuthRequestTokenURL>If AuthScheme=OAuth