Forum Discussion
Web Content - Access Method - WWW-Authenticate header doesn't contain a valid authorization URI
Hi timowille,
The workaround provided by the PG is:
To make this work with Power BI, the endpoint needs to return an URL which looks like
WWW-Authenticate: Bearer authorization_uri="https://login.windows.net/a1a2578a-8fd3-4595-bb18-7d17df8944b0/oauth2/authorize"
Where the GUID is the AAD tenant ID. This cannot be done entirely via configuration, it involves writing code on the service side.
Best Regards,
Qiuyun Yu
I'm a bit confused. My ASP.NET Core 2.0 app uses OpenIdConnect to authenticate against AzureAD. Specifically what changes do I need to make so that Power BI can correctly authenticate with my app and consume my JSON API?
tonjohn timowille o365spo wolfchan v-qiuyu-msft
I am getting same error when trying to access Azure analytics view from Power BI desktop using ODataFeeds URL.
I posted my question on this link, please help if you can help anything. I am kinda stuck right now.
It's been awhile since I worked in this space... If I recall correctly, I got around this issue by using an API Key instead of Oauth/OpenID.
I actually found a problem.
Active Directory was not setup for the Project I was trying to access using Organizational Credentials from PowerBI.I have used Personal Access Token to access the account from PowerBI while connecting through ODataFeed Data source URL, and it worked fine.