Allow authenticated access without a log on

I have reporting services set up and working, using Windows Authentication
and a web page with hyperlinks to the reports
(i.e. /Reports/Pages/Report.aspx?ItemPath=%2fReports%2MyReport).
This is on an Intranet and users who have not authenticated against the
domain get a username and password prompt (as we would expect).
I turns out that none of the users will authenticated and so they will all
get the log on prompt.
Is there any way to avoid the log in prompt ? (a simple way - I know I can
Implement my own Security Extension - but this is overkill for my needs).
I can't use anonymous access as different groups of people need to see
different reports (and be denied access to the others).
There are 4 groups and I already know which group each user is in. ( they do
a forms based sign in to a gateway application first)
Is it possible for instance to pass a username and password to a report and
have it authenticate that way ?
Someone suggested using the API:
dim lgn as new
Microsoft.SqlServer.ReportingServices2005.ReportingService2005()
lgn.LogonUser("Myusername" , "myPassword" , "" )
Is this possible ? if so how would the report then be launched ?
I don't mind hard coding a generic username and password in the asp.net code
behind for the page. ( I can set up 4 generic accounts, one for each group).
--
MartyYou should be able to do this. If the user is logged in to your PC in the
same domain as the RS server then they should not be prompted.
Anything special about the server? I.e. is it a domain controller. Is it
running sharepoint? Does it have a fixed IP address?
I ask about the fixed IP address because I saw this problem once when I had
a test server that was using DHCP.
Also, try adding your domain users and groups to a local group and then use
that local group when setting up your roles.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Marty" <smarty@.community.nospam> wrote in message
news:9B1A741B-88BB-494A-AA71-67C058D8C7D7@.microsoft.com...
>I have reporting services set up and working, using Windows Authentication
> and a web page with hyperlinks to the reports
> (i.e. /Reports/Pages/Report.aspx?ItemPath=%2fReports%2MyReport).
> This is on an Intranet and users who have not authenticated against the
> domain get a username and password prompt (as we would expect).
> I turns out that none of the users will authenticated and so they will all
> get the log on prompt.
> Is there any way to avoid the log in prompt ? (a simple way - I know I can
> Implement my own Security Extension - but this is overkill for my needs).
> I can't use anonymous access as different groups of people need to see
> different reports (and be denied access to the others).
> There are 4 groups and I already know which group each user is in. ( they
> do
> a forms based sign in to a gateway application first)
> Is it possible for instance to pass a username and password to a report
> and
> have it authenticate that way ?
> Someone suggested using the API:
> dim lgn as new
> Microsoft.SqlServer.ReportingServices2005.ReportingService2005()
> lgn.LogonUser("Myusername" , "myPassword" , "" )
> Is this possible ? if so how would the report then be launched ?
> I don't mind hard coding a generic username and password in the asp.net
> code
> behind for the page. ( I can set up 4 generic accounts, one for each
> group).
> --
> Marty|||"Also, try adding your domain users and groups to a local group and then use
that local group when setting up your roles."
Ah but my issue is that the users have not logged in to the domain when they
use my application. If I get them to log in to the domain first (as a test)
it all works seamlessley, with no prompts. However this is not how they
normally work (don't ask !).|||On Jan 8, 3:13=A0am, Marty <sma...@.community.nospam> wrote:
> "Also, try adding your domain users and groups to a local group and then u=se
> that local group when setting up your roles."
> Ah but my issue is that the users have not logged in to the domain when th=ey
> use my application. If I get them to log in to the domain first (as a test=)
> it all works seamlessley, with no prompts. However this is not how they
> normally work (don't ask !).
Along the same line, is there a way to use Windows Auth to not require
the log on screen every time we open
the Reporting Services web page rpt-serv/reports? The report server
is in domain I created a local group and added
mydomain\domain users to it? Hope this did not hijack your thread
Marty :)
Bob|||Hello Smart,
Since the reporting services is designed for the windows auth, you may need
to specify the domain account and password to log on to the domain.
So it will prompt the dialog.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
=====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||This makes absolutely no sense. You want them to be authenticated in RS
without logging in BUT they haven't logged in period. Then how would any
system in the world know who they are?
Sorry, this is just plain silly. If you aren't logged into a domain then you
aren't logged in and you are not authenticated and there is no way to be
authenticated without logging in.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Marty" <smarty@.community.nospam> wrote in message
news:ABBE4EB2-43DE-424F-9655-32D3FF57559D@.microsoft.com...
> "Also, try adding your domain users and groups to a local group and then
> use
> that local group when setting up your roles."
> Ah but my issue is that the users have not logged in to the domain when
> they
> use my application. If I get them to log in to the domain first (as a
> test)
> it all works seamlessley, with no prompts. However this is not how they
> normally work (don't ask !).
>