Suggest an Idea

[mfahlers]

For some Odata sources a custom header and/or query parameters is need for authentication.

It would be useful to support both in the connection creation on SaaS. 

One can add the query parameters to the root path, but this isn't unfortunally handled correctly for the getData method.

[chrisbrain]

@mfahlers Take your point about supporting custom query parameters.

Can you confirm you really need additional HTTP header support? As the connector already supports an 'Authorization' header.

[mfahlers]

 @chrisbrain Yes, the issue is with "none-standard" o-data authentication where an api-key is needed in the header or query parameter of a custom name.

I hacked a solution by force creating the connection with the API for a customer that neeed a api-key as query parameter. 

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.