Home Dashboard Directory Help
Search

Custom Security Extensions for SQL Server 2008 R2 Reporting (SSRS) - "Temporary User issue" by HYP84


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 774345
Opened: 12/14/2012 2:55:13 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

We are using Custom Security extension for user authentication (form based) for SSRS reporting access, we are getting an error

"The remote server returned an error: (500) Internal Server Error." for the first time click from web based application or even if access directly the report manager, for the second time click the report page gets loaded. When i tried to log the custom security extension code, on the first click we are getting "Temporary User" in GetUserInfo() method, so as its not a valid user to get the access we get http 500 error on the screen. This happens when we restart the Reporting Services and click on any of the reports in Report manager for the first time, but it works on the second click.

Have tested with many scenarios by tweaking the custom code and also logging the errors to trace the issue, but we get "Unknown" or "Temporary User" on the first click inside GetUserInfo() method. On the second click we get access to the reporting services which is strange.

How to handle temporary user in custom security extension code so that we can avoid the Http 500 error before it loads with proper sign on user. As per the analysis made, the issue is with Microsoft Product (SSRS), once the temporary user is created as per the CU3 release from Microsoft, but its not handled to check the proper user authentication until its found.

It seems Microsoft Product issue, any fix/resolution from Microsoft much appreciated.


Details
Sign in to post a comment.
Posted by Microsoft on 10/23/2013 at 11:19 AM
Hello,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.

Mariusz Cichomski
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
ReportServerService__12_14_2012_11_00_44.log (restricted) 12/14/2012 -