OK, I am not a programmer, but administrate the Report Server and its security. The .NET programmers want to connect direct to Report Server using WEB.CONFIG settings (see below).
<appSettings>
<add key="ConnectionString" value="Server=bpatlqddw\atlqddw01;Database=MP2_NET_STAGE;Integrated Security=False;User ID=MP2_Net;Password=xxxxx;Persist Security Info=false"/>
<add key="LogPath" value="\\bpga030wde01\wwwroot$\MP2_Net\Logs"/>
<add key="Url" value="http://bpga030wde01/MP2_Net/" />
What do I need to do to ensure their dynamic reports can run against my Report Server? What kind of rights do I assign the "MP2_Net" (above) login? All of this is outside the IIS-Report Server security environment? Do I assign rights via SQL Mgr? I cannot find any doco on this process.
What are the .NET programmers trying to do exactly? What is database MP2_NET_Stage? When you install reporting services and point it to a database it creates two databases, ReportServer and ReportServerTemp. Are they needing to access one of these?
|||ASP.NET application. MP2_NET & MP2_NET_Stage are the maintenance system databases (development at this time). They are using Report Server to build forms used by users, like work orders, PO's, etc. They are programically calling RS engine instead of using reports RDLs on web root.
I guess the question is: Can ASP.NET connect to Report Server using SQL Login instead of Windows Auth. via IIS layer? If so, is the WEB.CONFIG sample in above the way to go, and what are the options in script to accomplish. And, what do I need to do as DBA to get SQL security setup to allow it to work?
(sorry for misspells)
No comments:
Post a Comment