PowerBI REST API Authentication Failing after working for years

StandardSanders
Giga Guru

We've been using the method of pulling in data to PowerBI via a REST API Explorer generated call for various tables for the past 3+ years with no major issues. 

Last week we started getting an authentication failure message on the PowerBI side:

StandardSanders_0-1716903931884.png


I've tried re-entering the credentials and starting a new report from scratch just to test and no luck.

Additionally, any other outbound REST call I am using lately seems to be hit or miss at best. (Examples of some chat bots I'm testing):

StandardSanders_1-1716904128723.png

(I've attempted to adjust the sys properties on the size limitation and this never fixed the issue, I rolled back that change as well in case it was causing an issue).




I have a HI Support Ticket in but while I'm waiting for anything they could find wanted to see if anyone had ran into these issues as well and found a solution.

4 REPLIES 4

jonsan09
Giga Sage
Giga Sage

Have you tried testing the credentials through something like Postman? This should help narrow it done is the issue is on the PowerBI side or the credential/Servicenow side.

In Postman it does throw an auth error:

{
    "error": {
        "message": "User Not Authenticated",
        "detail": "Required to provide Auth information"
    },
    "status": "failure"

Community Alums
Not applicable

Hi @StandardSanders ,

 

It seems the issue is with the credentials only. Check if the credentials are correct which you are using.

As Jonson suggested try accessing the data from postman, if you are getting authentication error then check the previous creds. Try with new creds as well. If you are using a service account then check the permissions.

 

Also check ServiceNow table access and API access as well.

 

One more thing the error message mentions a Cluster URI (WABI-xxxxxXXXXXXXXXXXwindows.net). Make sure this URI is correct and accessible.

 

If my response has resolved your query, please consider giving it a thumbs up ‌‌ and marking it as the correct answer‌‌!

 

Thanks & Regards,

Sanjay Kumar

jonsan09
Giga Sage
Giga Sage

You might want to double check the configuration for the account.

  • Web services access only checked
  • Internal Integration User checked
  • Not locked
  • Role: snc_platform_rest_api_access
  • Role: Any role needed to perform needed operation on destination table (for example 'itil' to read/update records on 'incident' table)

Also might want to check security center/instance security center for failed login attempts for that account, in something or someone else changed the credentials.