We are trying to have SSRS2005 ready for production and I heard that
SSRS2005 upgrade to SSRS2005 is very difficult and SSRS2005 securty is very
poor.
IS that True?
Thanks,
As far as security you need to be more specific. I am not aware of security
issues. BUT, it depends on what you mean by it.
The way I look at security for my site, if you have rights to a report you
have rights to the data in the report. But, in a few cases where that isn't
true then I use the User!UserID global variable to restrict the access to a
report.
Now, if you have data that you need to restrict and you are doing it by the
parameter being passed into the report, then that can be modified.
The way to look at it is that RS uses role based security and is giving
rights to run a report. The data behind the report it is up to you on how
restrictive to make it. You can use User!UserID, you can use the login user
in the data source. By that I mean you add the user as a login to SQL Server
and then the credentials used for the data source is the user viewing the
report.
I don't do that. I have SQL Server in mixed mode and have a login that has
read only rights and give that use execute rights on appropriate stored
procedures. Then all reports use this special user for the credentials. The
person running the report is only used by RS to determine if they have the
right to run the report.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mecn" <me...@yahoo.com> wrote in message
news:eu63k1#fKHA...@TK2MSFTNGP05.phx.gbl...
"Bruce L-C [MVP]" <bruce_l...@hotmail.com> wrote in message
news:ebRM97%23fKH...@TK2MSFTNGP06.phx.gbl...
"Bruce L-C [MVP]" <bruce_l...@hotmail.com> wrote in message
news:ebRM97%23fKH...@TK2MSFTNGP06.phx.gbl...
That being said, RS 2008 is a great product and well worth the hassle of
upgrading.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mecn" <me...@yahoo.com> wrote in message
news:eOD93E$fKHA...@TK2MSFTNGP04.phx.gbl...
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mecn" <me...@yahoo.com> wrote in message
news:eOD93E$fKHA...@TK2MSFTNGP04.phx.gbl...
"Bruce L-C [MVP]" <bruce_l...@hotmail.com> wrote in message
news:eC%23Ufl$fKHA...@TK2MSFTNGP05.phx.gbl...
If in doubt, put them in VS08 and see what happens! :o)
HTH,
Scho
Thanks again
"Scho" <Schod...@hotmail.com> wrote in message
news:ed44af7f-5ad2-45bb...@n35g2000yqm.googlegroups.com...
Scho
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Scho" <Schod...@hotmail.com> wrote in message
news:ccc23c8a-0328-49e9...@m16g2000yqc.googlegroups.com...
Thanks
"Bruce L-C [MVP]" <bruce_l...@hotmail.com> wrote in message
news:erOZNuAg...@TK2MSFTNGP06.phx.gbl...
OK, so that gets the database secure. Now, RS support ssl so you would need
to configure it to use it:
http://msdn.microsoft.com/en-us/library/ms345223.aspx
Now remember, RS is a reporting solution. The key to PCI standard seems to
be a need to know. The reports would need to be designed that way. Using the
User!UserID to pass the user to your stored procedure that retrieves data.
This is not a parameter and cannot be spoofed.
It seems to me that RS can be used in compliance with the DCI standards IF
your organization does everything else it requires.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mecn" <me...@yahoo.com> wrote in message
news:#jT7CCBg...@TK2MSFTNGP06.phx.gbl...
"Bruce L-C [MVP]" <bruce_l...@hotmail.com> wrote in message
news:%23qrQ4aB...@TK2MSFTNGP05.phx.gbl...
"Bruce L-C [MVP]" <bruce_l...@hotmail.com> wrote in message
news:%23qrQ4aB...@TK2MSFTNGP05.phx.gbl...