Credentials for Reports and Subscriptions

I have run into a seemingly impossible wall with RS. I need to have the
â'domain\userâ' value to pass to my dataset parameter. From there, I need to
create data-driven subscription with the same report.
* If I use User!UserID to pass to the data source parameter, RS will not
allow subscriptions to be created
* If I use any kind of data source that does not have the user and pass
stored, RS will not allow you to create a data driven subscription. Why
wonâ't the data driven subscription simply allow me to choose another data
source that does have stored credentials?
Is there any way around these limitations?
Best regards,
Joel Blackthorne
Hewlett-Packard CompanyJoel,
The RS Windows Service (ReportServerService.exe) runs subscriptions in an
unattended mode so there is no interactive user. If RS would have allowed
you to be able to use User!Userid you would get the Windows identity of the
account the RS Windows Service runs under (not very useful as you would
probably agree).
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Joel" <Joel@.discussions.microsoft.com> wrote in message
news:FEFD3781-0374-42EA-B7FD-D83D207A308C@.microsoft.com...
> I have run into a seemingly impossible wall with RS. I need to have the
> 'domain\user' value to pass to my dataset parameter. From there, I need
to
> create data-driven subscription with the same report.
> * If I use User!UserID to pass to the data source parameter, RS will not
> allow subscriptions to be created
> * If I use any kind of data source that does not have the user and pass
> stored, RS will not allow you to create a data driven subscription. Why
> won't the data driven subscription simply allow me to choose another data
> source that does have stored credentials?
> Is there any way around these limitations?
> Best regards,
> Joel Blackthorne
> Hewlett-Packard Company|||the enterprise edition allow you to schedule a report for a bulk usage.
You have to create a query on a database to retreive the username, email,
paramaters values of your report parameter... (query NOT in the report, but
prepared by the administrator in the schedule definition)
when the schedule is reached, RS execute the query to retreive the user
names and send this name through a CUSTOM parameter (not the userid
parameter) and then RS render the report and email it.
another way is to create your own tool which produce the report in behalf of
a user, but you must store the user password anywhere!
then when you call the Report server service, you'll use this login name as
a credential instead-of the system user (or any other static account)
"Joel" <Joel@.discussions.microsoft.com> a écrit dans le message de news:
FEFD3781-0374-42EA-B7FD-D83D207A308C@.microsoft.com...
>I have run into a seemingly impossible wall with RS. I need to have the
> 'domain\user' value to pass to my dataset parameter. From there, I need
> to
> create data-driven subscription with the same report.
> * If I use User!UserID to pass to the data source parameter, RS will not
> allow subscriptions to be created
> * If I use any kind of data source that does not have the user and pass
> stored, RS will not allow you to create a data driven subscription. Why
> won't the data driven subscription simply allow me to choose another data
> source that does have stored credentials?
> Is there any way around these limitations?
> Best regards,
> Joel Blackthorne
> Hewlett-Packard Company|||Thanks for the feedback. However, in my opinion, User!UserID should return
the user id of the credentials that created the subscription then. At the
very least, Data-Driven subscriptions should let you handle this invalid
User!UserID condition by replacing it. As it stands, I donâ't see any way to
implement data-level security with RS if subscriptions are used. Can any one
suggest a way to achieve the goal outlined in the original post?|||Don't forget that there is always a back door leading to the .NET world.
Drop a pinch of custom code in your report, stir with some external .net
assemblies and escape the boundaries of the Report Server forever and ever.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Joel" <Joel@.discussions.microsoft.com> wrote in message
news:4607E1F7-EA33-4E0A-9A2B-9B48B4E5CE8C@.microsoft.com...
> Thanks for the feedback. However, in my opinion, User!UserID should
return
> the user id of the credentials that created the subscription then. At the
> very least, Data-Driven subscriptions should let you handle this invalid
> User!UserID condition by replacing it. As it stands, I don't see any way
to
> implement data-level security with RS if subscriptions are used. Can any
one
> suggest a way to achieve the goal outlined in the original post?