Passing Credentials in URL No Longer Working Sept 2021 Release

[Jarrod]

Hi All,

When passing through credentials in the url of a power bi report (http://user:password@reportserver/report/reportA), the web page will just display a spinning circle in the middle of the page. When refreshing the page, it will then work. This worked without issue in previous version.

[Petebro]

Can you try to use the format {DOMAIN}%5C{USERNAME}:password@<siteurl> instead of {user}%40{domain.com}:password@<siteurl>?

also if you URL Encode the .com in the username (i.e. petebro%40powerbi%2e.com for petebro@powerbi.com) I believe it will work.

If this is the problem we believe we have a fix, but this may be a potential workaround for the time being.

[Jarrod]

Thanks for the reponse.

Have tried a variety of URLs, including the method above, a variety of browsers and still could not get this to work. The same URL worked fine on our production report server running May 2021.

[Petebro]

Here we are able to reproduce the issue but only if the username has an unencoded '.' in it. Without revealing anything private can you give us the basic format you're trying to use? I assume it's something like:

http://<UserName>:<Password>@<Site> 

does the Username have domain\user or is it user@domain ?

[Jarrod]

For example sake only:

Report URL - http://12.345.678.9/reports/My%20Report

Domain - PBI

User - ReportUser

Pw - Password

What currently works with May is (Domain not required)

http://ReportUser:Password@http://12.345.678.9/reports/My%20Report

This doesn't work with Jan 2022.

Have also tried this but just spins. Open to any other suggestions on how you could get this to work. http://PBI%5CReportUser:Password@http://12.345.678.9/reports/My%20Report

Thanks.

[Petebro]

Thanks, very useful I'll investigate and let you know what we find.

[Petebro]

Quick question, can you remove the second HTTP:// and see if this works? Sorry there's some weird workaround for browsers that end up with us parsing url logic and this http may break that logic.

[Jarrod]

Sorry - Please disregard that. I've copied and pasted wrong. There is no second http.

Below is what I meant.

http://PBI%5CReportUser:Password@12.345.678.9/reports/My%20Report

Trying to give as much info as we can.

Using Edge ( 97.0.1072.55), this just spins. Both F5 and ctrl+F5 don't resolve. For some reason, you need to click in the address bar and hit enter. Once you do this, it displays.

Jan 2022

1 version of Chrome prompts for credentials (91.0.4472.77) I suspect this has something to do with the encoded DOMAIN\ as it also prompts in May 2021.

The other version (98.0.4758.82) passes credentials correctly but just spins as per Edge. Works fine in May 2021.

[Petebro]

Ah understood, I was going to ask if it was a typo and hoped it wasn't and we'd find the source of the issue. We are still investigating then.

[Jarrod]

Sorry mate, not that easy 🙂 

Thanks for your help thus far.

[Petebro]

one last suggestion while we dig into things. It could be caused by certain non-standard characters in the password. Would it be possible for you to URL encode the entire password and put that in the above example.

http://PBI%5CReportUser:{URL ENCODED PASSWORD}@12.345.678.9/reports/My%20Report

Sorry we are investigating things, but it seems like in most cases it's a special character causing this behavior.