Hi John,

How would I setup this on the SQL Server side of things? I selected "SQL
Server and Windows" as the Authentication method under the Security tab of
the SQL Server Registration. When I logon using the modified connection
string, I got this error...

"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."

thx,
-p

On Thu, 21 Mar 2002 19:23:58 -0500, BIGLEY,JOHN (HP-Roseville,ex1)
<john_bigleyHP.COM> wrote:

>If you do not want to pass a user id and password to SQL Server then use
>integrated security and it will connect using the processes security
>credentials. In this case whatever credentials you set up in COM+ for the
>application to run as will be used by SQL Server. To do this
add "Integrated
>Security=SSPI", for SQLOLEDB provider, to your connection string and do not
>use the user id and password key words. This is the only way I know of to
>prevent the passing of user id and password in the connection string.
>
>If this does not satisfy your requirements and you are concerned with the
>user id and password going across the wire in clear text, there are ways to
>encrypt this information. If you are interested in this possibility then
you
>should look at application roles in SQL Server.
>
>I hope this helps.
>
>John
>

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]