Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi,
I am looking for a way to perform an API call that requires client credential flow. My first approach is using the On-prem Gateway with a custom connector. The custom connector has the hardcoded client ID and client secret. This approach is not good enough sine we want to provide a generic custom connector to all of our clients. I want a way for the customer to store client ID and client secret from within PowerBI Service. My alternatives are using parameters or repurposing the user ID and password as client ID and secret. Any suggestions?
Edit: This is with the assumption that our clients will install their own On-prem gate way within their network. We will provide them the client credentials to consume our API.
thank you
I ended up relabeling windows authentication fields. Username to client id and Password to client secret. Is this a recommended practice to store client credentials in powerBI Service?
You will need to create a custom connector and then install the .mez on all gateway cluster members.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |