topic Re: Production Embedded Report Issue in Developer

Production Embedded Report Issue

Anonymous — Thu, 14 Jun 2018 23:39:36 GMT

Getting this message on an account;

{"error":"unauthorized_client","error_description":"AADSTS70002: Error validating credentials. AADSTS50053: You've tried to sign in too many times with an incorrect user ID or password.\r\nTrace ID: 6b4fa9ed-b473-4814-b3af-fda6a1da0900\r\nCorrelation ID: 88f09592-6d12-4e5d-b61d-11e34a412844\r\nTimestamp: 2018-06-14 14:49:57Z","error_codes":[70002,50053],"timestamp":"2018-06-14 14:49:57Z","trace_id":"6b4fa9ed-b473-4814-b3af-fda6a1da0900","correlation_id":"88f09592-6d12-4e5d-b61d-11e34a412844"}

The password or userID has not been changed, and the multiple attempt login issue is odd since when I login to the account on powerbi.com using same credentials, everything works fine.

This is now a problem on production.

Re: unauthorized_client Message - You've tried to sign in too many times.

ayakymets — Thu, 14 Jun 2018 15:42:48 GMT

The same issue. Also we received " AADSTS50053: You've tried to sign in too many times with an incorrect user ID or password", then try new account and get the next:

{"error":"invalid_grant","error_description":"AADSTS70002: Error validating credentials. AADSTS50126: Invalid username or password\r\nTrace ID: 3c4c42a0-c434-4044-bc8c-edd2a54e0f00\r\nCorrelation ID: ae299df8-50af-4009-8789-3f1a480bb3f2\r\nTimestamp: 2018-06-14 15:29:55Z","error_codes":[70002,50126],"timestamp":"2018-06-14 15:29:55Z","trace_id":"3c4c42a0-c434-4044-bc8c-edd2a54e0f00","correlation_id":"ae299df8-50af-4009-8789-3f1a480bb3f2"}

use it on production. HELP!!!

Re: Production Embedded Report Issue

v-jiascu-msft — Mon, 18 Jun 2018 09:12:54 GMT

Hi All,

1. What's the scenario? App owns data or User owns data?

2. What's the type of your own app? Native app or web app? If you register it as a web app but you only use one account, it could be returns errors.

Please refer to error-validating-credentials-aadsts50012-invalid-client-secret-is-provided and https://github.com/Azure/azure-keyvault-java/issues/5.

Best Regards,

Dale

Re: Production Embedded Report Issue

ayakymets — Mon, 18 Jun 2018 10:13:54 GMT

Hi.

1. Scenario: App owns data

2. Type of app: Native

Our code.

private async Task<AccessToken> GetAccessToken()
{
List<KeyValuePair<string, string>> formData = new List<KeyValuePair<string, string>>();
formData.Add(new KeyValuePair<string, string>("grant_type", "password"));
formData.Add(new KeyValuePair<string, string>("resource", this.powerBiConfiguration.ResourceUrl));
formData.Add(new KeyValuePair<string, string>("client_id", this.powerBiConfiguration.AppClientId));
formData.Add(new KeyValuePair<string, string>("username", this.powerBiConfiguration.UsernName));
formData.Add(new KeyValuePair<string, string>("password", this.powerBiConfiguration.Password.Trim()));

string oauthProviderUrl = this.powerBiConfiguration.OauthProviderUrl;
HttpClient httpClient = new HttpClient();
HttpContent content = new FormUrlEncodedContent(formData);
HttpResponseMessage responseMessage = await httpClient.PostAsync(oauthProviderUrl, content);

string responseData = string.Empty;

Stream data = await responseMessage.Content.ReadAsStreamAsync();
using (StreamReader reader = new StreamReader(data, Encoding.UTF8))
{
responseData = reader.ReadToEnd();
}

if (responseMessage.IsSuccessStatusCode)
{
return JsonConvert.DeserializeObject<AccessToken>(responseData);
}
else
{
string errorMessage = $"Access token for PowerBI was not received. Response: {responseData}";
this.logger.Error(errorMessage);
throw new Exception(errorMessage);
}
}

"PowerBiConfiguration": {
"ResourceUrl": "https://analysis.windows.net/powerbi/api",
"AppClientId": "12345678-9814-42fe-123456789",
"UsernName": "hiddenuser@organization.com",
"Password": "123123",
"GroupId": "12345678-d8b6-4af9-b607-123456789",
"OauthProviderUrl": "https://login.windows.net/common/oauth2/token"
},

Re: Production Embedded Report Issue

ayakymets — Mon, 18 Jun 2018 10:45:42 GMT

Hi,

1. Scenario: App owns data

2. We use Native App.

Also we grant all permissions for application.

Re: Production Embedded Report Issue

v-jiascu-msft — Mon, 18 Jun 2018 12:41:17 GMT

I would suggest you file a support ticket here.

Best Regards,

Dale

Re: Production Embedded Report Issue

Anonymous — Mon, 18 Jun 2018 17:48:00 GMT

1. How do I tell who owns the data? We have created it as an app, but the user itself holds the dataset.

2. It's a wep app and only one account has access / is the owner.

We changed it to a native app. Same issue.

Re: Production Embedded Report Issue

sibee75 — Mon, 18 Jun 2018 15:02:50 GMT

Just to add, we are experiencing the exact same issue, also affecting Production.

We have a ticket opened also.

We can also login with the same credentials via the PowerBI portal and nothing has changed code wise for several months.

This has let to 3 days downtime so far.

Re: Production Embedded Report Issue

v-jiascu-msft — Tue, 19 Jun 2018 01:21:26 GMT

Hi All,

Did you assign the App workspace to a capacity? It could be running out of resources without capacity. Please refer to embed-sample-for-customers#move-to-production.

Best Regards,

Dale

Re: Production Embedded Report Issue

Jeremypark — Tue, 19 Jun 2018 08:15:50 GMT

Hi There

We are experiencing exactly the same scenrio since last Thursday evening. Can access the reports etc on regular power bi portal.. but get the have tried to log in too many times with incorrect user name / password error when trying to receive a token. The user name and password have not changed, are correct and even when changing them and knowing that azure AD has synced, still same problem.

Where does the count for number of incorrect logins sit and where can it be reset? Have tried with two domain accounts that are both active and both get the same message..

Also trying the same via Postman and getting same result.

I notice two other organisations / users getting same issue since Thursday last week. and I saw a vague one liner from power bi that users may not be able to access their reports and an update would be communicated on Monday evening.. that was last night... We are still down.

I suspect something has changed on the back end side of Azure AD. ...

Surely there must be some way you can check what process is giving the too many times tried response...???

Re: Production Embedded Report Issue

sibee75 — Tue, 19 Jun 2018 09:18:24 GMT

Sounds very similar to us, we have a ticket open and are currently awaiting a further response.

Something must have changed backend. This has been happening since Friday AM at least.

Re: Production Embedded Report Issue

ayakymets — Tue, 19 Jun 2018 09:46:52 GMT

The same as you say.

We also still down.

Was tried recreate AD application and user grant permissions, but not work. Something happend on Azure side.

Maybe some inaccuracy was deployed with:

https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/whats-new

see May 2018

Re: Production Embedded Report Issue

karelmous — Tue, 19 Jun 2018 12:59:12 GMT

Since Friday morning, we have been encountering the exact same problem with on of our app. Problem occured in every deployment environment, including production. Been chasing the problem for days, but all setting seemed correct. Morever the code and deployment was not updated.

Hope Microsoft sorts things out on their side soon.

Re: Production Embedded Report Issue

Anonymous — Tue, 19 Jun 2018 15:34:13 GMT

Same issue here. DEV UAT PRD all affected.

Opened a MS ticket. Waiting for a response.

Re: Production Embedded Report Issue

Anonymous — Tue, 19 Jun 2018 19:55:40 GMT

We had the same issue that started Thursday evening / Friday morning. There was an Azure AD setting Microsoft changed on their end that impacted this functionality. I don't have the powershell script but their support helped us re-enable this feature so that our embedded reports work correclty. We're also going to update the way we authenticate to Azure AD so that it's not impacted in the future.

Here's the powershell.

$spId = "GUID HERE" (It is the object ID of the Service Principal. You can find it within Azure Active Directory > Enterprise Applications > Application you’re looking for > Properties > ObjectID)

$policy = New-AzureADPolicy -Definition @("{`"HomeRealmDiscoveryPolicy`":{`"AllowCloudPasswordValidation`":true}}") -DisplayName EnableDirectAuth -Type HomeRealmDiscoveryPolicy -IsOrganizationDefault $false

Add-AzureADServicePrincipalPolicy -Id $spId -RefObjectId $policy.Id

Re: Production Embedded Report Issue

Jeremypark — Wed, 20 Jun 2018 07:32:43 GMT

Thanks very much for sharing this. We are going to try it now. Will let you know.

Still not a word from anyone at PowerBi or Microsoft.....

Re: Production Embedded Report Issue

Jeremypark — Wed, 20 Jun 2018 09:10:47 GMT

We applied the script that you recommended All2Neat... solved our problem. We are back online.

Thank you so much for the heads up.

Re: Production Embedded Report Issue

ayakymets — Wed, 20 Jun 2018 13:54:06 GMT

Thanks for information. It resolve the problem. Now all works fine.

Re: Production Embedded Report Issue

Gnanasekar — Fri, 22 Jun 2018 09:43:15 GMT

Hi @Anonymous

I have tried with given script in my PowerShell. It is showing error.

Do I need any other permission/ subscription/ additional script to run this script?

Could you help me to fix this issue.

Gnanasekar

Re: Production Embedded Report Issue

Anonymous — Fri, 22 Jun 2018 13:24:25 GMT

Try the preview version for AzureAD. You may have to change this a little but this should do it. You may also have to uninstall the current module you have installed.

Install-Module -Name AzureADPreview