I've got an intranet page that connects to my SQL server, and I'm trying to force it to use NT Authentication when it does.
Already the Intranet uses NT Challenge-and-response authentication so that when I go to an intranet page I have to login. But then when I go to the page that connects to SQL, I get:
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user 'IUSR_COMPUTERNAME'.
Why isn't it passing MY user id? Why is it trying to use the anonymous IUSR id?Post your connection string. Also, what is your version of iis, sql server and windows ?|||Originally posted by rnealejr
Post your connection string. Also, what is your version of iis, sql server and windows ?
IIS 5 (Win2k Server) and SQL2k.
Turned out I needed to change the authentication on the website to BASIC instead of Native.|||Do you mean from integrated to basic ?|||Originally posted by rnealejr
Do you mean from integrated to basic ?
Yes, that is what I meant.
I was hoping to post the URL to the KB article that pointed me in that direction, but now I can't find it.. sorry everyone.|||When you find it - please post the article.|||Found it:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q247/9/31.ASP&NoWebContent=1sql
Showing posts with label authentication. Show all posts
Showing posts with label authentication. Show all posts
Friday, March 30, 2012
Wednesday, March 21, 2012
Passing authentication from PHP to reporting services
Hello,
My boss wants me to create a front end webpage for our Reporting
Services reports that customers can log onto through a webform. I'm a
PHP programmer, so I'd rather do this site and the authentication in
PHP than learn .NET. The main problem I see is finding a way to pass
the authentication to Reporting Services so that when a user runs a
report, they are not asked to enter their password a second time.
I don't even know where to start researching this problem... I've asked
in PHP forums and they passed me to you guys. Any ideas?
AndrewIf no one knows the answer to this, does anyone know a better place
that I could ask this question?|||andrewdmason@.gmail.com (andrewdmason@.gmail.com) writes:
> If no one knows the answer to this, does anyone know a better place
> that I could ask this question?
That would be microsoft.public.sqlserver.repotingsvcs.
If your local newserver does not carry it, it's available at
msnews.microsoft.com.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Setup anonymous authentication (instead of NT Challenge Response, the
default) for MS Reporting services and diallow all connections besides
the PHP server and then you don't have to worry about authentication at
all.
Erland Sommarskog wrote:
> andrewdmason@.gmail.com (andrewdmason@.gmail.com) writes:
> > If no one knows the answer to this, does anyone know a better place
> > that I could ask this question?
> That would be microsoft.public.sqlserver.repotingsvcs.
> If your local newserver does not carry it, it's available at
> msnews.microsoft.com.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp
Monday, March 12, 2012
Passing a RS authentication ticket/cookie to browser?
Hello,
It looks like the best solution for deploying my reports is through the
hybrid solution of using both URL access (a url over the internet to
render the report) and SOAP API access (a web service call to
authenticate via Forms Authentication, and a custom security
extension).
I'm reasonably clear about how to implement my RS Web service proxy,
and to gain access to the authentication ticket/cookie passed back from
RS once I am authenticated. I'd like to pass this authentication
ticket to a browser so I can use URL Access for the rest of my RS
session. How do I go about doing this?
I want the browser to take advantage of the RS HTML Viewer tool for
report rendering.
My Web application that's using reporting services is not an ASP.NET
application.
Any ideas would be a great help.
Thanks,
ZeroVerticalI am not sure what exactly your application topology is. Where are you
making the LogonUser API call? In general, you have to do the same thing
that Forms Authentication sample does in order to move the cookie from the
server call to the browser. If you have two applications, they have to be on
the same domain.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"zerovertical" <zerovertical@.yahoo.com> wrote in message
news:1132773532.572637.207830@.g47g2000cwa.googlegroups.com...
> Hello,
> It looks like the best solution for deploying my reports is through the
> hybrid solution of using both URL access (a url over the internet to
> render the report) and SOAP API access (a web service call to
> authenticate via Forms Authentication, and a custom security
> extension).
> I'm reasonably clear about how to implement my RS Web service proxy,
> and to gain access to the authentication ticket/cookie passed back from
> RS once I am authenticated. I'd like to pass this authentication
> ticket to a browser so I can use URL Access for the rest of my RS
> session. How do I go about doing this?
> I want the browser to take advantage of the RS HTML Viewer tool for
> report rendering.
> My Web application that's using reporting services is not an ASP.NET
> application.
> Any ideas would be a great help.
> Thanks,
> ZeroVertical
>
It looks like the best solution for deploying my reports is through the
hybrid solution of using both URL access (a url over the internet to
render the report) and SOAP API access (a web service call to
authenticate via Forms Authentication, and a custom security
extension).
I'm reasonably clear about how to implement my RS Web service proxy,
and to gain access to the authentication ticket/cookie passed back from
RS once I am authenticated. I'd like to pass this authentication
ticket to a browser so I can use URL Access for the rest of my RS
session. How do I go about doing this?
I want the browser to take advantage of the RS HTML Viewer tool for
report rendering.
My Web application that's using reporting services is not an ASP.NET
application.
Any ideas would be a great help.
Thanks,
ZeroVerticalI am not sure what exactly your application topology is. Where are you
making the LogonUser API call? In general, you have to do the same thing
that Forms Authentication sample does in order to move the cookie from the
server call to the browser. If you have two applications, they have to be on
the same domain.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"zerovertical" <zerovertical@.yahoo.com> wrote in message
news:1132773532.572637.207830@.g47g2000cwa.googlegroups.com...
> Hello,
> It looks like the best solution for deploying my reports is through the
> hybrid solution of using both URL access (a url over the internet to
> render the report) and SOAP API access (a web service call to
> authenticate via Forms Authentication, and a custom security
> extension).
> I'm reasonably clear about how to implement my RS Web service proxy,
> and to gain access to the authentication ticket/cookie passed back from
> RS once I am authenticated. I'd like to pass this authentication
> ticket to a browser so I can use URL Access for the rest of my RS
> session. How do I go about doing this?
> I want the browser to take advantage of the RS HTML Viewer tool for
> report rendering.
> My Web application that's using reporting services is not an ASP.NET
> application.
> Any ideas would be a great help.
> Thanks,
> ZeroVertical
>
Wednesday, March 7, 2012
Pass through Authentication
We have Reporting Services 2000 standard edition installed and everything works fine. You can log in and run reports and the Reporting Services security rolls work. The problem is when a user goes to the url of reporting services web server it prompts them for a login. They enter their Windows domain login and they get in. Is there a way to configure Reporting Services to use the user's Windows Domain login credentials (pass through) and not prompt for them, similar toSharePoint.Here is our configuration:
We have a NT Domain (not active directory) all servers and client machine’s are in the same domain.
IIS for Reporting Services is set to authenticate users by Integrated Windows authentication, Enable anonymous is unchecked.
Server is running Windows Server 2003 Web Edition
Database security utilizes sql server login and is storedin the data source.
We are also planning to move the access to Reporting Services through SharePoint.Don’t know if that will complicate this login issue
Thanks
Enable anonymous access should be checked. Username and password credentials should be given, uncheck Integrated Windows authentication|||I have a DotNetNuke portal running Reports from Reporting Services. I am having a problem because each time I access my ReportServer on a browser I am asked to authenticate myself. I am currently hosting my database on a hosting services company and I only have access to the Report Manager. Where should I define the access properties in the report manager for my report server?
The user I must use to authenticate is the main user which has full access to reports so this is not a viable solution.
Thanks for your help.
pass through authentication
I have a Windows 2003 member server that has SQL on it. I have a remote XP
machine in a workgroup that does have an account in the domain but does not
login to the domain (only used for OWA). Is it possible for this machine to
pass its authentication (same username and password) to the SQL server? I
used to be able to do this when the SQL server was on a domain controller.
Is there anyway to force this authentication through SQL?
Thoughts of ways for me to accomplish this??
Hi Bad,
Thank you for using Newsgroup.
Do you use the SQL SERVER 2000 or SQL SERVER 2005?
Actually SQL SERVER 2000 has two types of authentication: Windows
authentication and mixed authentication. If you do not use the domain
account to login in the Windows, you cannot use the Windows authentication
type to pass through the SQL SERVER, however you can use the SQL SERVER
authentication to access the SQL SERVER from the Windows XP machine. To do
so, you need to do the following things:
1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
Enterprise Manager, right click your server->click properties->Security,
select SQL Server and Windows under the Authentication)
2. Set up a SQL SERVER login account. (extend your server in the Enterprise
Manager, Security->Logins, set up your sa account, and you can use this sa
account to access the SQL SERVER)
If anything is unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I am using SQL 2000. It has worked in the past with windows authentication
when the SQL server was running on a domain controller. Is there any way to
pass the credentials through code?
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:beHHIyvKGHA.3696@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Thank you for using Newsgroup.
> Do you use the SQL SERVER 2000 or SQL SERVER 2005?
> Actually SQL SERVER 2000 has two types of authentication: Windows
> authentication and mixed authentication. If you do not use the domain
> account to login in the Windows, you cannot use the Windows authentication
> type to pass through the SQL SERVER, however you can use the SQL SERVER
> authentication to access the SQL SERVER from the Windows XP machine. To do
> so, you need to do the following things:
> 1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
> Enterprise Manager, right click your server->click properties->Security,
> select SQL Server and Windows under the Authentication)
> 2. Set up a SQL SERVER login account. (extend your server in the
> Enterprise
> Manager, Security->Logins, set up your sa account, and you can use this sa
> account to access the SQL SERVER)
> If anything is unclear, please feel free to let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Bad,
Do you mean both SQL SERVER and client machine are not in the domain now?
The following describes how SQL Server processes login accounts that
Windows authenticates:
1. When a user connects to SQL Server, the client opens a trusted
connection to SQL Server, which passes the user's Windows security
credentials to SQL Server.
Because the client opened a trusted connection, SQL Server knows that
Windows has already validated the login account.
2. If SQL Server finds the user's Windows user account or group account in
the list of SQL Server login accounts in the sysxlogins system table, it
accepts the connection.
SQL Server does not need to revalidate a password because Windows has
already validated it.
If SQL SERVER is in the domain, this trusted connection credential process
is finished in the AD. If SQL SERVER is not in the domain, you need to set
up a login account in the Windows server on which SQL SERVER locates, and
add this login account in the SQL SERVER login list. You cannot use the
domain account to access the SQL SERVER even if you set up a new account
with same username and password on the SQL SERVER because they have the
different SID. In this case, you can use the following two methods to
access the SQL SERVER. You might need to use these two methods even though
you use code to access the SQL SERVER.
1. Create a new login account on the server, and use this account to login
from the client machine.
2. Use the SQL SERVER authentication mode to access the database.
If anything is unclear, please let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||The SQL server is a member server in the domain.
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:EME5Jd5KGHA.224@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Do you mean both SQL SERVER and client machine are not in the domain now?
> The following describes how SQL Server processes login accounts that
> Windows authenticates:
> 1. When a user connects to SQL Server, the client opens a trusted
> connection to SQL Server, which passes the user's Windows security
> credentials to SQL Server.
> Because the client opened a trusted connection, SQL Server knows that
> Windows has already validated the login account.
> 2. If SQL Server finds the user's Windows user account or group account in
> the list of SQL Server login accounts in the sysxlogins system table, it
> accepts the connection.
> SQL Server does not need to revalidate a password because Windows has
> already validated it.
> If SQL SERVER is in the domain, this trusted connection credential process
> is finished in the AD. If SQL SERVER is not in the domain, you need to set
> up a login account in the Windows server on which SQL SERVER locates, and
> add this login account in the SQL SERVER login list. You cannot use the
> domain account to access the SQL SERVER even if you set up a new account
> with same username and password on the SQL SERVER because they have the
> different SID. In this case, you can use the following two methods to
> access the SQL SERVER. You might need to use these two methods even though
> you use code to access the SQL SERVER.
> 1. Create a new login account on the server, and use this account to login
> from the client machine.
> 2. Use the SQL SERVER authentication mode to access the database.
> If anything is unclear, please let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Bad,
Thank you for response.
Based on my further research, if SQL SERVER is the member server of domain,
and client does not login in with the domain account, you cannot use the
Windows authentication to access the SQL SERVER, even though you access the
server through the code. In such situation, you can only use the SQL
authentication to access the server. I suggest you create a SQL Server
login account, and use this account to access the database.
If you have anything unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
machine in a workgroup that does have an account in the domain but does not
login to the domain (only used for OWA). Is it possible for this machine to
pass its authentication (same username and password) to the SQL server? I
used to be able to do this when the SQL server was on a domain controller.
Is there anyway to force this authentication through SQL?
Thoughts of ways for me to accomplish this??
Hi Bad,
Thank you for using Newsgroup.
Do you use the SQL SERVER 2000 or SQL SERVER 2005?
Actually SQL SERVER 2000 has two types of authentication: Windows
authentication and mixed authentication. If you do not use the domain
account to login in the Windows, you cannot use the Windows authentication
type to pass through the SQL SERVER, however you can use the SQL SERVER
authentication to access the SQL SERVER from the Windows XP machine. To do
so, you need to do the following things:
1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
Enterprise Manager, right click your server->click properties->Security,
select SQL Server and Windows under the Authentication)
2. Set up a SQL SERVER login account. (extend your server in the Enterprise
Manager, Security->Logins, set up your sa account, and you can use this sa
account to access the SQL SERVER)
If anything is unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I am using SQL 2000. It has worked in the past with windows authentication
when the SQL server was running on a domain controller. Is there any way to
pass the credentials through code?
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:beHHIyvKGHA.3696@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Thank you for using Newsgroup.
> Do you use the SQL SERVER 2000 or SQL SERVER 2005?
> Actually SQL SERVER 2000 has two types of authentication: Windows
> authentication and mixed authentication. If you do not use the domain
> account to login in the Windows, you cannot use the Windows authentication
> type to pass through the SQL SERVER, however you can use the SQL SERVER
> authentication to access the SQL SERVER from the Windows XP machine. To do
> so, you need to do the following things:
> 1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
> Enterprise Manager, right click your server->click properties->Security,
> select SQL Server and Windows under the Authentication)
> 2. Set up a SQL SERVER login account. (extend your server in the
> Enterprise
> Manager, Security->Logins, set up your sa account, and you can use this sa
> account to access the SQL SERVER)
> If anything is unclear, please feel free to let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Bad,
Do you mean both SQL SERVER and client machine are not in the domain now?
The following describes how SQL Server processes login accounts that
Windows authenticates:
1. When a user connects to SQL Server, the client opens a trusted
connection to SQL Server, which passes the user's Windows security
credentials to SQL Server.
Because the client opened a trusted connection, SQL Server knows that
Windows has already validated the login account.
2. If SQL Server finds the user's Windows user account or group account in
the list of SQL Server login accounts in the sysxlogins system table, it
accepts the connection.
SQL Server does not need to revalidate a password because Windows has
already validated it.
If SQL SERVER is in the domain, this trusted connection credential process
is finished in the AD. If SQL SERVER is not in the domain, you need to set
up a login account in the Windows server on which SQL SERVER locates, and
add this login account in the SQL SERVER login list. You cannot use the
domain account to access the SQL SERVER even if you set up a new account
with same username and password on the SQL SERVER because they have the
different SID. In this case, you can use the following two methods to
access the SQL SERVER. You might need to use these two methods even though
you use code to access the SQL SERVER.
1. Create a new login account on the server, and use this account to login
from the client machine.
2. Use the SQL SERVER authentication mode to access the database.
If anything is unclear, please let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||The SQL server is a member server in the domain.
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:EME5Jd5KGHA.224@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Do you mean both SQL SERVER and client machine are not in the domain now?
> The following describes how SQL Server processes login accounts that
> Windows authenticates:
> 1. When a user connects to SQL Server, the client opens a trusted
> connection to SQL Server, which passes the user's Windows security
> credentials to SQL Server.
> Because the client opened a trusted connection, SQL Server knows that
> Windows has already validated the login account.
> 2. If SQL Server finds the user's Windows user account or group account in
> the list of SQL Server login accounts in the sysxlogins system table, it
> accepts the connection.
> SQL Server does not need to revalidate a password because Windows has
> already validated it.
> If SQL SERVER is in the domain, this trusted connection credential process
> is finished in the AD. If SQL SERVER is not in the domain, you need to set
> up a login account in the Windows server on which SQL SERVER locates, and
> add this login account in the SQL SERVER login list. You cannot use the
> domain account to access the SQL SERVER even if you set up a new account
> with same username and password on the SQL SERVER because they have the
> different SID. In this case, you can use the following two methods to
> access the SQL SERVER. You might need to use these two methods even though
> you use code to access the SQL SERVER.
> 1. Create a new login account on the server, and use this account to login
> from the client machine.
> 2. Use the SQL SERVER authentication mode to access the database.
> If anything is unclear, please let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Bad,
Thank you for response.
Based on my further research, if SQL SERVER is the member server of domain,
and client does not login in with the domain account, you cannot use the
Windows authentication to access the SQL SERVER, even though you access the
server through the code. In such situation, you can only use the SQL
authentication to access the server. I suggest you create a SQL Server
login account, and use this account to access the database.
If you have anything unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
pass through authentication
I have a Windows 2003 member server that has SQL on it. I have a remote XP
machine in a workgroup that does have an account in the domain but does not
login to the domain (only used for OWA). Is it possible for this machine to
pass its authentication (same username and password) to the SQL server? I
used to be able to do this when the SQL server was on a domain controller.
Is there anyway to force this authentication through SQL?
Thoughts of ways for me to accomplish this'?Hi Bad,
Thank you for using Newsgroup.
Do you use the SQL SERVER 2000 or SQL SERVER 2005?
Actually SQL SERVER 2000 has two types of authentication: Windows
authentication and mixed authentication. If you do not use the domain
account to login in the Windows, you cannot use the Windows authentication
type to pass through the SQL SERVER, however you can use the SQL SERVER
authentication to access the SQL SERVER from the Windows XP machine. To do
so, you need to do the following things:
1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
Enterprise Manager, right click your server->click properties->Security,
select SQL Server and Windows under the Authentication)
2. Set up a SQL SERVER login account. (extend your server in the Enterprise
Manager, Security->Logins, set up your sa account, and you can use this sa
account to access the SQL SERVER)
If anything is unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I am using SQL 2000. It has worked in the past with windows authentication
when the SQL server was running on a domain controller. Is there any way to
pass the credentials through code'
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:beHHIyvKGHA.3696@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Thank you for using Newsgroup.
> Do you use the SQL SERVER 2000 or SQL SERVER 2005?
> Actually SQL SERVER 2000 has two types of authentication: Windows
> authentication and mixed authentication. If you do not use the domain
> account to login in the Windows, you cannot use the Windows authentication
> type to pass through the SQL SERVER, however you can use the SQL SERVER
> authentication to access the SQL SERVER from the Windows XP machine. To do
> so, you need to do the following things:
> 1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
> Enterprise Manager, right click your server->click properties->Security,
> select SQL Server and Windows under the Authentication)
> 2. Set up a SQL SERVER login account. (extend your server in the
> Enterprise
> Manager, Security->Logins, set up your sa account, and you can use this sa
> account to access the SQL SERVER)
> If anything is unclear, please feel free to let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Bad,
Do you mean both SQL SERVER and client machine are not in the domain now?
The following describes how SQL Server processes login accounts that
Windows authenticates:
1. When a user connects to SQL Server, the client opens a trusted
connection to SQL Server, which passes the user's Windows security
credentials to SQL Server.
Because the client opened a trusted connection, SQL Server knows that
Windows has already validated the login account.
2. If SQL Server finds the user's Windows user account or group account in
the list of SQL Server login accounts in the sysxlogins system table, it
accepts the connection.
SQL Server does not need to revalidate a password because Windows has
already validated it.
If SQL SERVER is in the domain, this trusted connection credential process
is finished in the AD. If SQL SERVER is not in the domain, you need to set
up a login account in the Windows server on which SQL SERVER locates, and
add this login account in the SQL SERVER login list. You cannot use the
domain account to access the SQL SERVER even if you set up a new account
with same username and password on the SQL SERVER because they have the
different SID. In this case, you can use the following two methods to
access the SQL SERVER. You might need to use these two methods even though
you use code to access the SQL SERVER.
1. Create a new login account on the server, and use this account to login
from the client machine.
2. Use the SQL SERVER authentication mode to access the database.
If anything is unclear, please let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||The SQL server is a member server in the domain.
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:EME5Jd5KGHA.224@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Do you mean both SQL SERVER and client machine are not in the domain now?
> The following describes how SQL Server processes login accounts that
> Windows authenticates:
> 1. When a user connects to SQL Server, the client opens a trusted
> connection to SQL Server, which passes the user's Windows security
> credentials to SQL Server.
> Because the client opened a trusted connection, SQL Server knows that
> Windows has already validated the login account.
> 2. If SQL Server finds the user's Windows user account or group account in
> the list of SQL Server login accounts in the sysxlogins system table, it
> accepts the connection.
> SQL Server does not need to revalidate a password because Windows has
> already validated it.
> If SQL SERVER is in the domain, this trusted connection credential process
> is finished in the AD. If SQL SERVER is not in the domain, you need to set
> up a login account in the Windows server on which SQL SERVER locates, and
> add this login account in the SQL SERVER login list. You cannot use the
> domain account to access the SQL SERVER even if you set up a new account
> with same username and password on the SQL SERVER because they have the
> different SID. In this case, you can use the following two methods to
> access the SQL SERVER. You might need to use these two methods even though
> you use code to access the SQL SERVER.
> 1. Create a new login account on the server, and use this account to login
> from the client machine.
> 2. Use the SQL SERVER authentication mode to access the database.
> If anything is unclear, please let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Bad,
Thank you for response.
Based on my further research, if SQL SERVER is the member server of domain,
and client does not login in with the domain account, you cannot use the
Windows authentication to access the SQL SERVER, even though you access the
server through the code. In such situation, you can only use the SQL
authentication to access the server. I suggest you create a SQL Server
login account, and use this account to access the database.
If you have anything unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
machine in a workgroup that does have an account in the domain but does not
login to the domain (only used for OWA). Is it possible for this machine to
pass its authentication (same username and password) to the SQL server? I
used to be able to do this when the SQL server was on a domain controller.
Is there anyway to force this authentication through SQL?
Thoughts of ways for me to accomplish this'?Hi Bad,
Thank you for using Newsgroup.
Do you use the SQL SERVER 2000 or SQL SERVER 2005?
Actually SQL SERVER 2000 has two types of authentication: Windows
authentication and mixed authentication. If you do not use the domain
account to login in the Windows, you cannot use the Windows authentication
type to pass through the SQL SERVER, however you can use the SQL SERVER
authentication to access the SQL SERVER from the Windows XP machine. To do
so, you need to do the following things:
1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
Enterprise Manager, right click your server->click properties->Security,
select SQL Server and Windows under the Authentication)
2. Set up a SQL SERVER login account. (extend your server in the Enterprise
Manager, Security->Logins, set up your sa account, and you can use this sa
account to access the SQL SERVER)
If anything is unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I am using SQL 2000. It has worked in the past with windows authentication
when the SQL server was running on a domain controller. Is there any way to
pass the credentials through code'
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:beHHIyvKGHA.3696@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Thank you for using Newsgroup.
> Do you use the SQL SERVER 2000 or SQL SERVER 2005?
> Actually SQL SERVER 2000 has two types of authentication: Windows
> authentication and mixed authentication. If you do not use the domain
> account to login in the Windows, you cannot use the Windows authentication
> type to pass through the SQL SERVER, however you can use the SQL SERVER
> authentication to access the SQL SERVER from the Windows XP machine. To do
> so, you need to do the following things:
> 1. Enable the SQL SERVER to use the mixed mode. (in the SQL SERVER
> Enterprise Manager, right click your server->click properties->Security,
> select SQL Server and Windows under the Authentication)
> 2. Set up a SQL SERVER login account. (extend your server in the
> Enterprise
> Manager, Security->Logins, set up your sa account, and you can use this sa
> account to access the SQL SERVER)
> If anything is unclear, please feel free to let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Bad,
Do you mean both SQL SERVER and client machine are not in the domain now?
The following describes how SQL Server processes login accounts that
Windows authenticates:
1. When a user connects to SQL Server, the client opens a trusted
connection to SQL Server, which passes the user's Windows security
credentials to SQL Server.
Because the client opened a trusted connection, SQL Server knows that
Windows has already validated the login account.
2. If SQL Server finds the user's Windows user account or group account in
the list of SQL Server login accounts in the sysxlogins system table, it
accepts the connection.
SQL Server does not need to revalidate a password because Windows has
already validated it.
If SQL SERVER is in the domain, this trusted connection credential process
is finished in the AD. If SQL SERVER is not in the domain, you need to set
up a login account in the Windows server on which SQL SERVER locates, and
add this login account in the SQL SERVER login list. You cannot use the
domain account to access the SQL SERVER even if you set up a new account
with same username and password on the SQL SERVER because they have the
different SID. In this case, you can use the following two methods to
access the SQL SERVER. You might need to use these two methods even though
you use code to access the SQL SERVER.
1. Create a new login account on the server, and use this account to login
from the client machine.
2. Use the SQL SERVER authentication mode to access the database.
If anything is unclear, please let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||The SQL server is a member server in the domain.
"Warner wang" <v-warnw@.microsoft.com> wrote in message
news:EME5Jd5KGHA.224@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Do you mean both SQL SERVER and client machine are not in the domain now?
> The following describes how SQL Server processes login accounts that
> Windows authenticates:
> 1. When a user connects to SQL Server, the client opens a trusted
> connection to SQL Server, which passes the user's Windows security
> credentials to SQL Server.
> Because the client opened a trusted connection, SQL Server knows that
> Windows has already validated the login account.
> 2. If SQL Server finds the user's Windows user account or group account in
> the list of SQL Server login accounts in the sysxlogins system table, it
> accepts the connection.
> SQL Server does not need to revalidate a password because Windows has
> already validated it.
> If SQL SERVER is in the domain, this trusted connection credential process
> is finished in the AD. If SQL SERVER is not in the domain, you need to set
> up a login account in the Windows server on which SQL SERVER locates, and
> add this login account in the SQL SERVER login list. You cannot use the
> domain account to access the SQL SERVER even if you set up a new account
> with same username and password on the SQL SERVER because they have the
> different SID. In this case, you can use the following two methods to
> access the SQL SERVER. You might need to use these two methods even though
> you use code to access the SQL SERVER.
> 1. Create a new login account on the server, and use this account to login
> from the client machine.
> 2. Use the SQL SERVER authentication mode to access the database.
> If anything is unclear, please let me know. Thank you!
> Sincerely,
> Warner Wang
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Bad,
Thank you for response.
Based on my further research, if SQL SERVER is the member server of domain,
and client does not login in with the domain account, you cannot use the
Windows authentication to access the SQL SERVER, even though you access the
server through the code. In such situation, you can only use the SQL
authentication to access the server. I suggest you create a SQL Server
login account, and use this account to access the database.
If you have anything unclear, please feel free to let me know. Thank you!
Sincerely,
Warner Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)