i have implemented the Form Based Authentication for my Report Server(SSRS),
now my question is how to remove authentication for a single report.
i have deployed one report in the report server and i want to view it from external network without asking any username/password for that particular report..!
if i gave <authentication mode="None" /> in web.config file this will remove all the authentication which i don't want.
i tried this also but it's not working
https://www.linkedin.com/pulse/ssrs-anonymous-authentication-problem-solved-frans-van-der-geer
please help..
Related
I was told that Tableau server requires these 2 SingleLogoutService elements below that are not in the SAML metadata from Azure AD. If I add these, it works.
Is it supported to manually add these?
Is there a plan to add these in the future to the metadata on AAD?
<SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://login.microsoftonline.com/f4094948-32fb-4c4b-b659-63b99f22a08d/saml2" />
<SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP" Location="https://login.microsoftonline.com/f4094948-32fb-4c4b-b659-63b99f22a08d/saml2" />
WE never heard this as a requirement from the Tableau side. Can you please specify that you are using Tableau server or cloud version? If this is server then which version of it?
You can add more Logout URLs int he metadata as you need but note that Azure AD does not support SOAP biding or Redirect binding for SAML Logout. Only POST biding is supported.
I know this is repeat question, but I have searched almost all the threads about this and have not found any solution to my problem. Some of threads show a solution like:
&dsu:DataSourceName=username&dsp:DataSourceName=password
But this doesn't work for me. What value should I give for DataSourceName?FolderName/SharedDataSourceName or only SharedDataSourceName? For username and password do I need to provide Windows username and password for where the report server is installed? I tried all possible combinations, but nothing has worked.
I am showing this report using Kendo Window & iFrame controls in an Angular SPA application. iFrame is being passing SSRS URL and showing report.
Firstly why does the dsu: & dsp: method not work for me? And if it's working but not secured as passing username and password then what other approaches are available for URL based reporting service?
In the RDL of the report and on your SSRS reports manager you should be able to set a DataSource and authentication type. If you have the RDL looking at a shared DataSource then put the DataSource in the same folder as the RDL and you can click 'Manage' on it and enter the credentials/authentication type you want
I can access my reports through
http://mymachine:808/Reports
or
http://localhost:808/Reports
but not
http://myhost.mydomain.com:808/Reports
even when I have myhost.mydomain.com map to 127.0.0.1 in the host file. It was keep asking user name and password, but the same user name and password works fine in other ways to access.
How to fix this?
Update
It prompts to type in user name and password, but just to pop up again. So there is no way to get into the page with the broken URL.
This is consistent in at least 2 browsers: Firefox 47.0, and Edge 25.10586.0.0
Also, I didn't have Report Manager installed, here is my menu of Reporting services configuration manager:
From the hint in comments the issues is in the Reporting Services.
I was using the default settings, but MSDN said you can have different authentication types. I checked my reportserver.config file and I was using NTLM. Change it to use basic authentication solves the problem.
My guess of the reason, is that the browser will send a "Host" property for every request, and as this is inconsistent with NTLM's "domain", so Reporting Services reject the authentication. However, when switch to basic authentication, it simply pass the credential to Windows, so now it accepts.
References:
Authentication Types in Reporting Services
How to: Configure Basic Authentication in Reporting Services
You could try adding a new URL for Report Manager. To do this
Open Reporting Services Configuration Manager
Select Report Manager URL
Click Advanced
Click Add to add details
Here's a screenshot to help.
I am trying to access the security settings in the ASP.NET Web Configuration tool.
I read the MSDN tutorial at : MSDN
I also found how to make the tool run from this answer
I am getting the following error when I click the 'Security' link on the web config tool page:
There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.
The following message may help in diagnosing the problem: Unable to connect to SQL Server database.
I did find a similar question, but the message to diagnose the problem is different in my case.
Can someone please help ?
Thanks.
Update:
Didn't resolve the issue yet, but tried it on a different machine.
Before showing the ASP.NET Web Configuration tool page, it asks for username and password. I tried following this answer, but it still asks for username and password.
Which username and password is required here ?
Thanks.
I have a PerformancePoint dashboard running in MOSS 2007 portal. The dashboard consists of one SSRS 2005 report, running in SharePoint Integrated mode.
NT Authority\Authenticated Users have read permissions to the report library containing the SSRS report, the dashboard, and the report library containing the dashboard.
Users that attempt to access the dashboard receive the following error message:
The permissions granted to user
'DOMAIN\firstname.lastname' are
insufficient for performing this
operation. (rsAccessDenied)
Users that then click on the direct link to the report in MOSS will see the report with no problem. Subsequent visits to the dashboard show the report with no problem.
The report is using a data source that is located one folder up from the report location. The report has been updated to point to the correct shared data source after deployment. Both the report and the data source have been published. The data source is using stored credentials, with a domain service account that has been set to Use as Windows credentials. This service account is serving other reports in other areas with no problem.
Edit:
Ok, I've gotten a lot more information on this problem. The request is never actually being made to the data source. The user comes in to the dashboard and requests a report for the first time using their kerberos token identifying themselves. The report looks in the Report Server database and finds that they are not listed in the users table and generates this rsAccessDenied error. Once they view the report directly their name is in this table and they never have the problem again.
Unfortunately, removing the user from the Users table in the RS database doesn't actually cause this error to happen again.
Everything I've read says that when you run a Report Server in MOSS integrated mode all your permissions are handled at the MOSS report library level, and all Auth users have permissions to the report library, as stated earlier. Any ideas?
It sounds like the dashboard page is not passing credentials to the report server. Because you stated if the user hits the report directly it works and then if they go through the dashboard it works. So does it stop working after a certain period, indicating a cached session?
I would look carefully at the properties on the dashboard in performance point to see if it is passing credentials or trying to use anonymous. I hope this isn't a case of double hop and Kerberos :(
I'm not sure if this is actually the same issue, but you could double check that the data sources are set to "Approved", not "Pending". It's a stretch, but it's worth a shot.
I implemented a work-around:
created a fake report
on the page with my report, created a content editor web part consisting of the following:
<iframe style="display:none;" src="https://link/to/my/report.rdl"></iframe>
I tested with another user that was experiencing the error, and they are no longer experiencing the error with my new and improved page.
I know this is a kludgy, and might even be dependent on the loading order of the page. Therefore, I would really like to find out what's causing this issue so I can fix it for good.
Edit:
I don't want to accept my own answer, since it's just a work-around. If anyone can post anything relevant to the user name placed into the Report Server DB and how that relates to SharePoint Integrated mode, you'll get the bounty.