Forum Discussion
Report Server Custom Authentication
- 8 years ago
Thank you v-qiuyu-msft for comments. It seems I had wrong URL in CodeGroup membership. When I changed URL from
C:\Program Files\Microsoft Power BI Report Server\PBIRS\PowerBI\Microsoft.Samples.ReportingServices.CustomSecurity.dll
to C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\bin\Microsoft.Samples.ReportingServices.CustomSecurity.dll, it seems the permission problem has resolved and I can register new user.
However when login goes successfull and navigate to ReportServer Web Portal URL, it shows HTTP 500 Internal Server ERROR. Is there any way to investigate and find-out root cause of it?
Thanks once again,
M. Irfan
- 8 years ago
Thanks pbx This link help me to find out the exact problem. So for rest of the community here is the reason of HTTP 500 error
When we added "machineKey" in <RSPATH>\ReportServer\web.config path, everytime when pbix service restarted it remove this key. The step mentined here need to be updated v-qiuyu-msft. Best solution is to add machinekey in "machine.config" file inside <system.web> and then restart machine
32-bit
%windir%\Microsoft.NET\Framework\[version]\config\machine.config
64-bit
%windir%\Microsoft.NET\Framework64\[version]\config\machine.config
Note: This entry may create conflicts/problem for other application running on same machine so be careful.
Hope this will help. Thank you.
Have you seen this? Take note of the very last comment.
https://github.com/Microsoft/Reporting-Services/issues/26
Thanks pbx This link help me to find out the exact problem. So for rest of the community here is the reason of HTTP 500 error
When we added "machineKey" in <RSPATH>\ReportServer\web.config path, everytime when pbix service restarted it remove this key. The step mentined here need to be updated v-qiuyu-msft. Best solution is to add machinekey in "machine.config" file inside <system.web> and then restart machine
32-bit
%windir%\Microsoft.NET\Framework\[version]\config\machine.config
64-bit
%windir%\Microsoft.NET\Framework64\[version]\config\machine.config
Note: This entry may create conflicts/problem for other application running on same machine so be careful.
Hope this will help. Thank you.
- pbx8 years agoHelper V
The proper documentation about custom security extensions can be found here:
That means for PBIRS the machine key should be placed in \ReportServer\rsReportServer.config. However according to the following link, a bug in PBIRS, at least up to this version 1.1.6514.9163 (Build 14.0.600.434), exists that requires putting they keys in machine.config. Given that there's been two minor relases after that, could you please confrim if the bug still exists in the latest release, Version 1.1.6551.5155 (Build 14.0.600.438)?
- malikirfan288 years agoHelper II
Dear pbx, Ok I will check new version on fresh mahine and then update here.
However right now when a new registered user login successfully, PBIRS display error:
You are not allowed to view this folder. Contact your administrator to obtain the necessary permissions.
The Builten (Windows) Administrator acccount does not work with custom security so how can I login as Administrator and grant permission to custom user? If I revert back to Windows Authentication then builten Administrator work and I can change Site Setting, but at this time PBIRS does not found any custom user name. When I try to add custom user name in "Add User or Group" field it give error, "such user or group does not exist".
Any idea?
- Anonymous8 years agoNot applicable
I installed Power Bi Report Server - Evaluation, Product Version 15.0.2.378 and I still had to update the machine config to get it to work with the custom security example.
- Anonymous8 years agoNot applicable
Thank you so much for this post. Adding the machine key to the machine.config file worked.
- Anonymous8 years agoNot applicable
This worked for me.
Here are the details:
edited C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config
Add machinekey under system.web
I used Visual Studio to edit machine.config. Must start VS as admin.
Restart computer, restart rs service