Forbidden 403 error for datasets/group through REST API (postman)

[mani1215]

Hi Team,

I am creating oAuth token with below request payload and getting oAuth bearer token. When i use that token to list data sets, groups, add rows to dataset tables, we are getting the 403 Forbidden access. 

POST https://login.windows.net/common/oauth2/token

grant_type : client_credentials

resource: https://analysis.windows.net/powerbi/api

client_secret: XXXX

client_id: XXXX

This issue is blocking us to update data set tables data, do we have any documentation to get oAuth beare token from REST API (postman)

Thanks

Mani

[Eric_Zhang]

---

@mani1215 wrote:

Hi Team,

I am creating oAuth token with below request payload and getting oAuth bearer token. When i use that token to list data sets, groups, add rows to dataset tables, we are getting the 403 Forbidden access. 

POST https://login.windows.net/common/oauth2/token

grant_type : client_credentials

resource: https://analysis.windows.net/powerbi/api

client_secret: XXXX

client_id: XXXX

This issue is blocking us to update data set tables data, do we have any documentation to get oAuth beare token from REST API (postman)

Thanks

Mani

---

@mani1215

Based on my test, the token from grant_type "client-credentials" doesn't work. Try to use grant_type: password, the token works in my test.

[Anonymous]

@Eric_Zhang I am able to make it work with UserNamePassword Credential but unable to communicate with the Power BI service with clientCredential. Below is my code snippet. credential is of type UserPasswordCredential and creds is of type ClientCredential, instantiated with clientID and client secret.

Snippet

var authenticationContext = new AuthenticationContext("https://login.windows.net/common/oauth2/authorize/");
//var authenticationResult = await authenticationContext.AcquireTokenAsync("https://analysis.windows.net/powerbi/api", clientId, credential);
var authenticationResult = await authenticationContext.AcquireTokenAsync("https://analysis.windows.net/powerbi/api", creds);

 We would like to use the ClientCredential just to make sure we don't have to update the password every 3 months(governed by policies)