Custom authorization with multiple authorities

The LogonUser function takes a third parameter used to identify an
authority for the user name (I assume this is the same intention as the
realm in HTTP authentication). I assumed the idea was to allow
Reporting Services to enable log-ins from users in multiple user
databases. For example, if we are using RS to serve reports on each of
our customers' virtual web sites, then each customer has its own user
database.
The problem is, the IAuthorizationExtension interface does not use
authority strings. I assume the idea is that user names must be unique
amongst all the authorities, perhaps by adding the authority name as a
prefix (e.g., the user "bill" in the user database of customer "Acme"
might have a user name acme.bill for the purposes of authorization. I
assume further that the way this is is achieved is that, after LogonUser
is called as LogonUser("bill", password, "Acme"), then GetUserInfo
returns a userIdentity of "acme.bill" rather than plain "bill". Does
this sound plausible?I wrote:
> I
> assume further that the way this is is achieved is that, after LogonUser
> is called as LogonUser("bill", password, "Acme"), then GetUserInfo
> returns a userIdentity of "acme.bill" rather than plain "bill". Does
> this sound plausible?
After some experimentation, it seems to me that GetUserInfo is *not*
consulted when generating the ticket cookie. I guess this means I need
to feed the qualified user names in to LogonUser, and always use the
same authority string.

Custom assemblies and accessing report parameters

I am trying to access the datasource parameters (connection string etc)
through the report with the intention of using them to fire off a stored
procedure at the end of the report. The parameters will be passed to a custom
assembly will execute the sp to update several status flags in the database.
The assembly is done and updates the status parameters, however the
connection string is currently hard coded.
Is there any way to access these parameters direct from the report, or an
interface I could implement in my assembly that would allow me access to them?Please see my response on your other thread with the same title.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Benugo" <Benugo@.discussions.microsoft.com> wrote in message
news:484BE97E-55FF-456B-94C7-C7AECE733CF1@.microsoft.com...
> I am trying to access the datasource parameters (connection string etc)
> through the report with the intention of using them to fire off a stored
> procedure at the end of the report. The parameters will be passed to a
custom
> assembly will execute the sp to update several status flags in the
database.
> The assembly is done and updates the status parameters, however the
> connection string is currently hard coded.
> Is there any way to access these parameters direct from the report, or an
> interface I could implement in my assembly that would allow me access to
them?