How to Login to Report Server 2016 - reporting-services

I'm trying to wrap my head around the SSRS login. Here is my test setup.
SSRS 2016 installed on hostname: Testrs16
ReportServer Database installed on hostname: Server2
I'm launching ReportBuilder on Server2 and trying to connect and login to the report server (see screenshot). What login it typically used in this case? Thanks!
ssrs login

Authentication to your Report Server database is configured via the Report Server Configuration Manager. This will be the same for all users connecting to the Report Server.
Note: This is not the source of your data in your reports, but is where SSRS stores catalog information, user settings, and other internal components
Authentication Types for users connecting to the portal, web api, or soap endpoints are defined in your RSReportServer.config file as either RSWindowsNTLM (default), RSWindowsNegotiate, RSWindowsBasic, or Custom.
Once the user is authenticated (who are they?), then the authorization (what can they do) is defined in the folder management for catalog item security by assigning roles to users or groups.
The other authentication that is required for rendering a report is authenticating to your report's data source. This is defined in either the Report's Data Source or in a Shared Data Source. Either of these can be configured in the data source management page on the portal.

Related

Windows authentication and subscriptions in SSRS

I've got an ssrs report server setup and the data sources are set to use the user's windows login. However when I try to setup a subscription it says it can't because the credentials aren't stored in the data source. Is there no way to have a subscription that uses a generic account but when run interactively it uses Windows username
I use a database account for running all of the reports. You'll have to set this up in each database. Then I have report folder permissions associated to Active Directory groups. I also use a domain service account for deploying the reports and setting up the subscriptions. That way if a member of the BI team leaves the company and their account is deactivated the subscription will still run.
Data Source Example:

SSRS subscription with Oracle data source

We have an SSRS with Oracle as data source. Creating report Works, but creating subscriptions doesn't.
On the Data Source configuration page,i use Oracle internal user and enabled "Credentials stored securely on the report server". If i click Test Connectiong, it says the connectiong was succesful.
Creating a subscription gives the error "Subscriptions cannot be created because the credentials used to run the report are not stored, or if a linked report, the link is no longer valid."
Something i found out is that the reports i create have as data source :
Data Source=localhost;Initial Catalog=Production and Windows Integrated Security as credentials.
Shouldn't Oracle be the data source and what can i do to correctly configure the subscriptions?
seems datasource credentials are your windows credentials, try changing it to your oracle database credentials. check below link for more information of connection strings.
https://learn.microsoft.com/en-us/sql/reporting-services/report-data/oracle-connection-type-ssrs

Microsoft Reporting Server SSRS 2012 Architecture

We are planning to deploy reporting service using Microsoft Reporting Server 2012. As I understand it, there will be three components;
Database (SQL Server)
SSRS (Reporting Server)
IIS (Web front end) - SharePoint (alternate Front end)
In setting up the Proof-of-Concept, the dev installed SSRS and SQL Server on same box (let's call it the DB server) and is redirecting client browser to a URL on DB Server from web front end.
Is it possible to architect the solution so that the web front end is the only destination for client browsers, SSRS lives on its own dedicated server separate from both the Web server and the DB Server?
How will authentication work in this scenario? We are using integrated authentication using Enterprise AD.
Configurations I have used in the past are these:
SQL Server on one server; SSRS native on another server. Users accessed reports via the SSRS Report Manager web UI that comes with SSRS.
SQL Server on one server; SSRS install in SharePoint Hosting mode on another server. Users accessed reports via SharePoint.
I am not 100% sure what you mean by “web front end is the only destination for client browsers”. If you mean that the end user only hits a web server, and not the database server to get reports, then either one of the above will work. If you have an existing intranet site that you want to host reports in, you can do so via web parts, if you are using MS technologies. You will still need SSRS setup somewhere so you can deploy reports, and the web part would read from it. Or, you can continue the redirect to either Report Manager or SharePoint if you go that route.
As far as authentication: the authentication between SSRS and SQL Server is usually done via an AD (Active Directory) user/service account that SSRS runs under, and also has access to the databases is uses on the SQL Server.
The authentication that allows users to browse and execute reports is usually done via AD as well. You can add all users to a central AD group and give that group Browser permissions on the SSRS server. This authentication would still apply if you use web parts to host reports outside of SSRS Report Manager.
The authentication that SSRS uses to pull the data that ends up showing in reports is usually SQL Server authentication, or whatever authentication that your data source supports where you can send a user name and password (which is stored within a shares data source on SSRS).
More Info

SSRS 2012 - Prompting for credentials

I have a 2012 SSRS report with the following requirements:
When accessed (run), it must prompt for Windows (AD) credentials because users will be launching it from "group workstations" where the current username is "NurseStationNorth" (so I can't use integrated security).
I'd prefer to hard-code the data-source credentials to ensure that the database connection has all the rights/permissions needed for the report.
Because the report displays user-specific data, I need to pass the authenticated username (e.g. MyDomain\CoolUser) as a parameter to the report. I attempted to use the User!UserId global variable but it seemed to reflect the workstation username and not the credentials entered upon running the report.
I understand how to "Manage" the deployed SSRS report via SQL Server Reporting Services "Home" webpage, to configure the Data Source to always prompt for Windows credentials, but I'm not sure this is the behavior I'm seeking.
Any insight is appreciated.
Thanks,
Mike

Why do I have to enter credentials in Report Builder for shared data source?

I am using Report Server 2012 and Report Builder 3.0. I defined a Analysis Services Data Source on the server where I provide windows credentials to access the server.
When I want to add a dataset in Report Builder based on this data source I have to enter credentials. Why? They are defined in the shared data source on the server....
My understanding was, that the data source defined on the report server will use the credentials defined in the data source and not the credentials of the calling client application.