Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi. I've built a custom data connector to a REST API that uses OAuth. Currently the client_id and client_secrets used by the OAuth authentication are stored in spearate files as per the samples provided by Microsoft here.
Is it possible for the client_id to and client_secret to be provided by the user filling in a paramater prompt during authentication once the connector has been deployed in Power BI, or must these credentials be stored in the connector's mez package?
Hi @Quicky,
Here is a similar thread in which a solution is mentioned. Could you go to check if it helps in your scenario?
I have managed to sort this out.
I have accomplished an alpha solution that covers the authentication part + fetches data.
Currently tested with mock data.
https://github.com/AmirSasson/pardot-powerbi-connector
I might add some paging mechanism to support large scale data fetch.
Regards
Thanks for that link - I'm glad someone else has encountered this! I guess it's not officially possible at the moment.
The workarounds mentioned in that thread are:
Since the eventual roadmap must surely involve the distribution of generic connectors through the Office Store, I'd be interested to know how it will be possible to incorporate the secure storage of API key, client IDs and client secrets into the authentication procedure going forward. The only working solution in that thread (the second one above) isn't particularly user friendly or universally applicable to all authentication methods.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.