I have a report which has been running for almost four years that uses multiple API calls to a cloud service to pull in several different data elements in both JSON and CSV formats. These data sources are on a nightly scheduled refresh and have been working just fine until recently. I noticed as I was asked to look into an upcoming modification that the refreshes are now failing with an error stating the credentials are not valid. Thinking the bearer token in the connection string may have expired, I opened my local copy of the report in Desktop and tested the connection, and it worked just fine.
The only notes I can find refer to PBIRS not supporting Web.Page and Web.BrowserContents methods for scheduled refresh, but this connection uses Web.Contents, which is supported. The connection authentication is Anonymous as the bearer token is embedded in the connection string, and this has been working until I noticed this issue.
Has something changed in how the Report Server manages these types of connections? It's imperative I find a solution as my client is somewhat anxious to have their reporting stay up to date, and will have an effect on the future development they are considering.
