Office web components basic authentication impersonation

Hi,

I have a question regarding office web components 10.0/11.0.

I've searched various forums without finding an answer.

My question is whether it's possible to use office web components with basic authentication so that the OWC uses the specified identity (basic authentication) to authenticate against AS 2000 instead of using the identity of the user that is currently logged on to the machine?

My problem is that we external users that aren't members of our AD that shall have access to AS2000. And when OWC uses the machine login instead of the basic authentication login the authentication fails.

And also, is it any difference when using OWC with AS 2000 compared to AS 2005?

I know that one solution that I've gotten to work with AS 2005 is to use HTTP connection, but then I must specify user name and password which isn't an ideal solution for us. It would be better if integrated security could be used.

Looking forward toward you answer

Regards,

Johan.

Moved as this seems to be AS related.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Not sure I get your question.

If you are trying to access Analysis Services using OWC through HTTP connection you got choice to ether use Basic Auth or Integrated. (Of cource there is anonymous)
If your user is coming from outside of AD, you got to use Basic Auth.
With Basic Auth your users needs to provide username and password, only integrated Auth works knows how to re-use existing user credentials.

HTH
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hello Edward,

My users are coming from outside of the AD. But I've created AD accounts for them to use when they login using basic authentication.

If I use HTTP connection will I have to add a username and a password in the connectionstring?

Is it possible for the user to connect to the AS database without using HTTP connection?

My experience of using OWC is that OWC will not use the identity of the web page but instead use the user's machine account.

/Johan

|||

You will need to provide usernames and passwords for Basic Auth to work.

As for protocols options to connect to Analysis Services: You have a choice of HTTP or TCP/IP.

Using TCP/IP you can establish connection to Analysis Server only using integrated windows authentication.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

> If I use HTTP connection will I have to add a username and a password in the connectionstring?

No, I think you can set up the virtual folder that holds the HTTP connectivity stuff using Basic Auth and it will then prompt and in this case you should not put the username/password in the connection string.

> My experience of using OWC is that OWC will not use the identity of the web page but instead use the user's machine account.

This is correct. OWC is an ActiveX component and it executes on the client machine (not on the server). It creates it's own connection back to the AS server. Therefore if you have Basic Auth setup on the website and on the HTTP connection, the users will get prompted twice. The only way around this would be to either:

allow anonymous access to the web page, and let the AS HTTP connection do the prompting setup an explicit username/password in the connection string, but this means you cannot apply role based security as AS only "sees" one user connecting.

Odd authentication issues

I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.
Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>

Odd authentication issues

I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>

Odd authentication issues

I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>

ODBC, VB, SQL Authentication

How do I connect to SQL Server using VB6? I will be setting up the ODBC for
SQL using SQL Authentication. Is there a way that I do not hard code the
username and password in the VB program? I wouldn't like to have login
screen to ask for the user's credentials. Thanks
Hi NS
You can very well prompt users to key in user name and pwd instead of
hardcoding. Infact it is the best technique to do that.
do not provide username and pwd in the connection string, try to pass
parameters that were entered in the popped up text box.
please let me know if u have any questions
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
"NS" wrote:

> How do I connect to SQL Server using VB6? I will be setting up the ODBC for
> SQL using SQL Authentication. Is there a way that I do not hard code the
> username and password in the VB program? I wouldn't like to have login
> screen to ask for the user's credentials. Thanks
|||NS,
I would recommend using Windows Authentication instead of SQL Server
Authentication if that is at all possible - more secure.
HTH
Jerry
"NS" <NS@.discussions.microsoft.com> wrote in message
news:076393DE-4439-4169-87E5-595A545226DC@.microsoft.com...
> How do I connect to SQL Server using VB6? I will be setting up the ODBC
> for
> SQL using SQL Authentication. Is there a way that I do not hard code the
> username and password in the VB program? I wouldn't like to have login
> screen to ask for the user's credentials. Thanks
|||I was thinking after setting up the DSN for SQL with SQL Authentication, you
could simply point to the dsn in your visual basic code when connecting to
the database (ADODB.Connection...). I thought one need not provide the user
and password again. So, that isn't true?
"Chandra" wrote:
[vbcol=seagreen]
> Hi NS
> You can very well prompt users to key in user name and pwd instead of
> hardcoding. Infact it is the best technique to do that.
> do not provide username and pwd in the connection string, try to pass
> parameters that were entered in the popped up text box.
> please let me know if u have any questions
> --
> best Regards,
> Chandra
> http://chanduas.blogspot.com/
> http://www.SQLResource.com/
>
> "NS" wrote:
|||You can also can force the prompt in code - it's a property
that's exposed for the connection object in ADO.
YourConnection.Properties("Prompt") = adPromptAlways
YourConnection.Open ...etc just specifying driver, server
and database.
-Sue
On Tue, 25 Oct 2005 07:37:12 -0700, "NS"
<NS@.discussions.microsoft.com> wrote:

>How do I connect to SQL Server using VB6? I will be setting up the ODBC for
>SQL using SQL Authentication. Is there a way that I do not hard code the
>username and password in the VB program? I wouldn't like to have login
>screen to ask for the user's credentials. Thanks
|||"NS" <NS@.discussions.microsoft.com> wrote in message
news:1E3777C8-3B00-4A83-8C63-7DBD9D3CE30A@.microsoft.com...
> I was thinking after setting up the DSN for SQL with SQL Authentication,
you
> could simply point to the dsn in your visual basic code when connecting to
> the database (ADODB.Connection...). I thought one need not provide the
user
> and password again. So, that isn't true?
Yes, it is true. You need to declare the following in your VB app:
Private Declare Function SQLReadFileDSN Lib "ODBCCP32.DLL" _
(ByVal lpszFileName As String, _
ByVal lpszAppName As String, _
ByVal lpszKeyName As String, _
ByVal lpszString As String, _
ByVal cbString As Long, _
ByRef pcbString As Long) As Long
Lookup the function SQLReadFileDSN in MSDN for examples of how to use it and
what the parameters mean.
[vbcol=seagreen]
> "Chandra" wrote:
ODBC for[vbcol=seagreen]
the[vbcol=seagreen]
login[vbcol=seagreen]

ODBC, VB, SQL Authentication

How do I connect to SQL Server using VB6? I will be setting up the ODBC for
SQL using SQL Authentication. Is there a way that I do not hard code the
username and password in the VB program? I wouldn't like to have login
screen to ask for the user's credentials. ThanksHi NS
You can very well prompt users to key in user name and pwd instead of
hardcoding. Infact it is the best technique to do that.
do not provide username and pwd in the connection string, try to pass
parameters that were entered in the popped up text box.
please let me know if u have any questions
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"NS" wrote:

> How do I connect to SQL Server using VB6? I will be setting up the ODBC f
or
> SQL using SQL Authentication. Is there a way that I do not hard code the
> username and password in the VB program? I wouldn't like to have login
> screen to ask for the user's credentials. Thanks|||NS,
I would recommend using Windows Authentication instead of SQL Server
Authentication if that is at all possible - more secure.
HTH
Jerry
"NS" <NS@.discussions.microsoft.com> wrote in message
news:076393DE-4439-4169-87E5-595A545226DC@.microsoft.com...
> How do I connect to SQL Server using VB6? I will be setting up the ODBC
> for
> SQL using SQL Authentication. Is there a way that I do not hard code the
> username and password in the VB program? I wouldn't like to have login
> screen to ask for the user's credentials. Thanks|||I was thinking after setting up the DSN for SQL with SQL Authentication, you
could simply point to the dsn in your visual basic code when connecting to
the database (ADODB.Connection...). I thought one need not provide the user
and password again. So, that isn't true?
"Chandra" wrote:
[vbcol=seagreen]
> Hi NS
> You can very well prompt users to key in user name and pwd instead of
> hardcoding. Infact it is the best technique to do that.
> do not provide username and pwd in the connection string, try to pass
> parameters that were entered in the popped up text box.
> please let me know if u have any questions
> --
> best Regards,
> Chandra
> http://chanduas.blogspot.com/
> http://www.SQLResource.com/
> ---
>
> "NS" wrote:
>|||You can also can force the prompt in code - it's a property
that's exposed for the connection object in ADO.
YourConnection.Properties("Prompt") = adPromptAlways
YourConnection.Open ...etc just specifying driver, server
and database.
-Sue
On Tue, 25 Oct 2005 07:37:12 -0700, "NS"
<NS@.discussions.microsoft.com> wrote:

>How do I connect to SQL Server using VB6? I will be setting up the ODBC fo
r
>SQL using SQL Authentication. Is there a way that I do not hard code the
>username and password in the VB program? I wouldn't like to have login
>screen to ask for the user's credentials. Thanks|||"NS" <NS@.discussions.microsoft.com> wrote in message
news:1E3777C8-3B00-4A83-8C63-7DBD9D3CE30A@.microsoft.com...
> I was thinking after setting up the DSN for SQL with SQL Authentication,
you
> could simply point to the dsn in your visual basic code when connecting to
> the database (ADODB.Connection...). I thought one need not provide the
user
> and password again. So, that isn't true?
Yes, it is true. You need to declare the following in your VB app:
Private Declare Function SQLReadFileDSN Lib "ODBCCP32.DLL" _
(ByVal lpszFileName As String, _
ByVal lpszAppName As String, _
ByVal lpszKeyName As String, _
ByVal lpszString As String, _
ByVal cbString As Long, _
ByRef pcbString As Long) As Long
Lookup the function SQLReadFileDSN in MSDN for examples of how to use it and
what the parameters mean.
[vbcol=seagreen]
> "Chandra" wrote:
>
ODBC for[vbcol=seagreen]
the[vbcol=seagreen]
login[vbcol=seagreen]

ODBC, VB, SQL Authentication

How do I connect to SQL Server using VB6? I will be setting up the ODBC for
SQL using SQL Authentication. Is there a way that I do not hard code the
username and password in the VB program? I wouldn't like to have login
screen to ask for the user's credentials. ThanksHi NS
You can very well prompt users to key in user name and pwd instead of
hardcoding. Infact it is the best technique to do that.
do not provide username and pwd in the connection string, try to pass
parameters that were entered in the popped up text box.
please let me know if u have any questions
--
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"NS" wrote:
> How do I connect to SQL Server using VB6? I will be setting up the ODBC for
> SQL using SQL Authentication. Is there a way that I do not hard code the
> username and password in the VB program? I wouldn't like to have login
> screen to ask for the user's credentials. Thanks|||NS,
I would recommend using Windows Authentication instead of SQL Server
Authentication if that is at all possible - more secure.
HTH
Jerry
"NS" <NS@.discussions.microsoft.com> wrote in message
news:076393DE-4439-4169-87E5-595A545226DC@.microsoft.com...
> How do I connect to SQL Server using VB6? I will be setting up the ODBC
> for
> SQL using SQL Authentication. Is there a way that I do not hard code the
> username and password in the VB program? I wouldn't like to have login
> screen to ask for the user's credentials. Thanks|||I was thinking after setting up the DSN for SQL with SQL Authentication, you
could simply point to the dsn in your visual basic code when connecting to
the database (ADODB.Connection...). I thought one need not provide the user
and password again. So, that isn't true?
"Chandra" wrote:
> Hi NS
> You can very well prompt users to key in user name and pwd instead of
> hardcoding. Infact it is the best technique to do that.
> do not provide username and pwd in the connection string, try to pass
> parameters that were entered in the popped up text box.
> please let me know if u have any questions
> --
> best Regards,
> Chandra
> http://chanduas.blogspot.com/
> http://www.SQLResource.com/
> ---
>
> "NS" wrote:
> > How do I connect to SQL Server using VB6? I will be setting up the ODBC for
> > SQL using SQL Authentication. Is there a way that I do not hard code the
> > username and password in the VB program? I wouldn't like to have login
> > screen to ask for the user's credentials. Thanks|||You can also can force the prompt in code - it's a property
that's exposed for the connection object in ADO.
YourConnection.Properties("Prompt") = adPromptAlways
YourConnection.Open ...etc just specifying driver, server
and database.
-Sue
On Tue, 25 Oct 2005 07:37:12 -0700, "NS"
<NS@.discussions.microsoft.com> wrote:
>How do I connect to SQL Server using VB6? I will be setting up the ODBC for
>SQL using SQL Authentication. Is there a way that I do not hard code the
>username and password in the VB program? I wouldn't like to have login
>screen to ask for the user's credentials. Thanks|||"NS" <NS@.discussions.microsoft.com> wrote in message
news:1E3777C8-3B00-4A83-8C63-7DBD9D3CE30A@.microsoft.com...
> I was thinking after setting up the DSN for SQL with SQL Authentication,
you
> could simply point to the dsn in your visual basic code when connecting to
> the database (ADODB.Connection...). I thought one need not provide the
user
> and password again. So, that isn't true?
Yes, it is true. You need to declare the following in your VB app:
Private Declare Function SQLReadFileDSN Lib "ODBCCP32.DLL" _
(ByVal lpszFileName As String, _
ByVal lpszAppName As String, _
ByVal lpszKeyName As String, _
ByVal lpszString As String, _
ByVal cbString As Long, _
ByRef pcbString As Long) As Long
Lookup the function SQLReadFileDSN in MSDN for examples of how to use it and
what the parameters mean.
> "Chandra" wrote:
> > Hi NS
> >
> > You can very well prompt users to key in user name and pwd instead of
> > hardcoding. Infact it is the best technique to do that.
> >
> > do not provide username and pwd in the connection string, try to pass
> > parameters that were entered in the popped up text box.
> >
> > please let me know if u have any questions
> >
> > --
> > best Regards,
> > Chandra
> > http://chanduas.blogspot.com/
> > http://www.SQLResource.com/
> > ---
> >
> >
> >
> > "NS" wrote:
> >
> > > How do I connect to SQL Server using VB6? I will be setting up the
ODBC for
> > > SQL using SQL Authentication. Is there a way that I do not hard code
the
> > > username and password in the VB program? I wouldn't like to have
login
> > > screen to ask for the user's credentials. Thanks

ODBC via Windows authentication

Hello,

We have an internal application that accesses SQL Server 2000 via ODBC.
The connecton is established with user id and password. We recently
received a business request to allow the software to work with Windows
authentication scheme going forward. This implies that users will no
longer have passwords to login to the database. The Windows PC would
take care of the authentication.

Is there a way (perhaps a connection string) to allow ODBC to connect
to the database in this new environment? I would appreciate any tips
or pointers.<tunity5@.yahoo.com> wrote in message
news:1105712559.798067.299450@.c13g2000cwb.googlegr oups.com...
> Hello,
> We have an internal application that accesses SQL Server 2000 via ODBC.
> The connecton is established with user id and password. We recently
> received a business request to allow the software to work with Windows
> authentication scheme going forward. This implies that users will no
> longer have passwords to login to the database. The Windows PC would
> take care of the authentication.
> Is there a way (perhaps a connection string) to allow ODBC to connect
> to the database in this new environment? I would appreciate any tips
> or pointers.

There are some sample connection strings for trusted connections here:

http://www.able-consulting.com/MDAC...verForSQLServer

Simon|||I think you can call SQLConnect with an empty user name and password
information.
Also, for using SQLDriverConnect, try to add "Trusted_Connection = yes" into
your connect string.

t> The connecton is established with user id and password. We recently
t> received a business request to allow the software to work with
t> Windows authentication scheme going forward. This implies that users
t> will no longer have passwords to login to the database. The Windows
t> PC would take care of the authentication.

Igor Shekalev, http://www.sqledit.com, SQL editor with ODBC support

ODBC SQL Server Driver

Good Afternoon,
I had a mistake when I tried to connect to query analyser with an NT authentication, the message was: "Cannot generate SSPI context." I tried to connect to another machine, and it's been connected.
Can anyone help me?
Thanks.
ConceioWhich version of sql server are you using (including service pack) ?|||Originally posted by rnealejr
Which version of sql server are you using (including service pack) ?

Our SGBD is SQL Server 2000, service pack 2.|||Check your services for the following and verify that it is running (on the client attempting to make the connection) -

NT LM Security Support Provider