Can anybody explain the detailed step by step procedure for form authentication in sql reporting services 2008 r2 .I am new to ssrs ,I need details about how to configure in rsreportserver,web.config files and how to write coding for authentication for ssrs .Is there any special procedure for ssrs forms authentication and how to verify in C# code and where to redirect ?
See these links for some examples & other information from Microsoft:
http://msdn.microsoft.com/en-us/library/xdt4thhy(v=vs.100).aspx
http://msdn.microsoft.com/en-us/library/cc281383.aspx
http://msftrsprodsamples.codeplex.com/wikipage?title=SS2008R2%21Security%20Extension%20Sample
http://www.codeproject.com/Articles/675943/SSRS-Forms-Authentication
The high level summary is:
Create custom authentication process (login form, credential source, backend code to wire it all together)
Extend LogonUser() method of SSRS webservice
Modify configs to expect forms auth, and allow your custom code to run within the app pool
I've done this a few times now, and honestly, it's easier than it sounds.
Related
We have a dashboard deployed on a Power BI Server On-premise. So no Azure AD solutions please.
We would like to display this dashboard on an Extranet Web Application that uses Forms Authentication for its users. We currently use iFrame or redirect URL access, since those are the only options.
We don't want the Users to login again to view reports since they have already logged in to the Application. They are currently being prompted.
How can we use a common credential(preferably AD account) to authenticate/authorize each dashboard view? We want to be able to change the credentials programmatically.
You'll have to implement a custom authentication extension. You should be able to use the existing SSRS documentation, given that Power BI Report Server is essentially a direct superset of SSRS. If you want to use AD accounts, you'll have to establish a normal AD authentication flow in your application, as well as pass on a valid cookie over to the SSRS side of things. Microsoft has pretty extensive documentation, as well as samples on this:
Documentation on custom authentication:
https://learn.microsoft.com/en-us/sql/reporting-services/extensions/security-extension/authentication-in-reporting-services
Repository with samples:
https://github.com/Microsoft/Reporting-Services/tree/master/CustomSecuritySample
I'm trying to publish SSRS 2016 Web Service & Web Portal via Web Application Proxy and AD FS on Win 2012 R2.
What configuration do I need to have on the SSRS side in order to be able to access reports via URL and WAP?
Does anyone has found a step-by-step guide? I've been googling for a few days without luck.
Thanks,
I'm not sure if there was any special SSRS configuration required, but here are the steps for getting the SSRS web portal published through the WAP.
One issue we had was the report path was being removed from the querystring when a report was requested. The solution was to encode the report path portion of the URL.
Create a standard Relying Party Trust in ADFS with no claims set and the endpoint and identifier set to https://example.com/ReportServer/.
Publish an endpoint in WAP with ADFS pre-authentication and set external and internal URL to https://example.com/ReportServer/.
Use a URL like the following to access a report, https://example.com/ReportServer/Pages/ReportViewer.aspx/?%2fHR-Reports%2fQ1-Report&rs:Command=Render
UPDATE:
Unfortunately, this doesn't appear to be the case. There seems to be a bug with the WAP related to truncating the report path. If you have already authenticated with ADFS and then access a report (e.g. https://example.com/ReportServer/Pages/ReportViewer.aspx?/HR-Reports/Q1-Report&rs:Command=Render), you are redirected to ADFS because the authn token is not yet set for your reports service provider (SP) as the "EdgeAccessCookie" cookie.
The reports SP (usually WAP really) redirects you to ADFS for a token with your return URL in the query string. You've already authenticated to ADFS, so you're given a token for the SP and redirected back to your SP, but the issue is the report path is no longer present in the query string of your SP's URL (https://example.com/ReportServer/Pages/ReportViewer.aspx/?rs:Command=Render&authToken=xyz). This causes an error at your report server.
If you then access the original URL again though (https://example.com/ReportServer/Pages/ReportViewer.aspx?/HR-Reports/Q1-Report&rs:Command=Render), you already have your authn token for the SP and your browser presents it to your SP as the EdgeAccessCookie cookie. In this case you are not redirected to ADFS and you are able to access your report as expected. Of course, this is less than ideal however having to access your report a 2nd time.
I want to be able to deploy a report and this deploy should take care of the an email subscription and set the report run schedule; I shouldn't have to manually create a subscription later on and if a new subscription is to be applied, I should be able to update the subscription with report deploy only. If somebody could provide a generic subscription element template to copy and paste in the rdl file, will be a great help.
Subscriptions are not part of the RDL file.
There is no way you can do what you want if you want it to deploy using right-click:deploy.
If you are using some automated process for deployment (rs.exe, SSRS webservice etc), you can set up subscriptions, but it would be a lot of work
From everything I have found, I do not see how you can create a subscription. I have found a lot on altering an existing subscription though:
https://msdn.microsoft.com/en-us/library/dn747196.aspx#bkmk_how_to
No instruction of rCREATING via PS, only mods:
https://msdn.microsoft.com/en-us/library/ms156307(v=sql.130).aspx
you may be able to create the subscription ion a STAGE environment then transfer it to Prod as part of your post deployment
I'm working on a "SQL Server Reporting Services 2008" server. I have a report which contains content every 2-7 days. I have an abonnoment, which is sending me this report every night via E-Mail. This is very annoying, when there is no content within the attached file.
Is there any way, how to don't send the subscribed Mail, when there is no content?
I found this link, but I guess this is just included in SSRS2008R2, but not in SSRS2008.
Any help or ideas?
Thanks!
if you have enterprise edition, you can use data driven subscriptions. you just change the view behind the data driven subscription to not return any rows if there is no data.
if you don't have enterprise edition, you should remove the schedule in SSRS report manager (set it to run once) and then trigger the subscription using the Reportserver.dbo.AddEvent procedure.
You call this procedure with the subscription id and it will execute this subscription. you have to write some code that determines if there is data in this report and calls the addevent procedure if there is.
I have some dashboards with Reporting Services and SharePoint, some need parameters some of them do not need parameters. I want to create something standard(I've think in a standard report) that receives all the possible parameters of the dashboards.
My idea: In my report will exist a button with the name Suscribe, this button displays a report or form that will receive all the important parameters directly from the report that called it, in this new report or form the user will choose the periodicity, write his mail and/or a CC.
I've seen some examples, but this examples need to create a subscription before hand, and I have more than 100 reports and differents users can create differents subscriptions.
http://www.sqlservercentral.com/articles/Development/datadrivensubscriptions/2432/
http://www.sqlservercentral.com/articles/Development/2824/
I appreciate your help.
If you are using Sql Server Enterprise Edition then you have support for data driven subscriptions in which case you can define sp's or a query that returns email addresses for the given report. If you are not using EE the data driven subscriptions are not supported:(