advice

Hi,

Apologies if this sounds dumb but I'm very new to this.

I'm just trying to create a simple login page (
http://aarkenuk.co.uk/barnesg/login.php) In my MySQL databases I have the
correct database selected, but it's the users I'm struggling with. You get
like a front end with my hosting space (CpanelX) and in there I've created
user "admin" password "admin" but I cannot seem to login.

This is what I see in the front end..

Users in test
barnes_admin (Privileges: ALL PRIVILEGES)

Connection Strings
Perl $dbh =
DBI->connect("DBI:mysql:barnes_test:localhost","barnes_admin","<PASSWORD
HERE>");
PHP $dbh=mysql_connect ("localhost", "barnes_admin", "<PASSWORD
HERE>") or die ('I cannot connect to the database because: ' .
mysql_error());
mysql_select_db ("barnes_test");

Is there anything more I need to do? Do you login with barnes_admin or just
admin? (I've tried both) and why does it created barnes_admin and not just
admin? Also what are the connection strings for? do I need to do anything
with these?

Thanks very much in advance for any advice..

Gary"gjb" <Kookookaachoo@.hotmail.com> wrote in message
news:CkZLf.26271$wl.7873@.text.news.blueyonder.co.u k...
> Hi,
> Apologies if this sounds dumb but I'm very new to this.
> I'm just trying to create a simple login page (
> http://aarkenuk.co.uk/barnesg/login.php) In my MySQL databases I have the
> correct database selected, but it's the users I'm struggling with. You get
> like a front end with my hosting space (CpanelX) and in there I've created
> user "admin" password "admin" but I cannot seem to login.

This is a Microsoft SQL Server group, not MySQL group so you're probably not
going to find as much help here as you'd ilke.

However, I would say taht you probably don't want an admin being able to
access your database from a webpage simply for security reasons.

> This is what I see in the front end..
> Users in test
> barnes_admin (Privileges: ALL PRIVILEGES)
> Connection Strings
> Perl $dbh =
> DBI->connect("DBI:mysql:barnes_test:localhost","barnes_admin","<PASSWORD
> HERE>");
> PHP $dbh=mysql_connect ("localhost", "barnes_admin", "<PASSWORD
> HERE>") or die ('I cannot connect to the database because: ' .
> mysql_error());
> mysql_select_db ("barnes_test");
>
> Is there anything more I need to do? Do you login with barnes_admin or
just
> admin? (I've tried both) and why does it created barnes_admin and not just
> admin? Also what are the connection strings for? do I need to do anything
> with these?
> Thanks very much in advance for any advice..
> Gary|||gjb (Kookookaachoo@.hotmail.com) writes:
> Apologies if this sounds dumb but I'm very new to this.
> I'm just trying to create a simple login page (
> http://aarkenuk.co.uk/barnesg/login.php) In my MySQL databases I have the
> correct database selected, but it's the users I'm struggling with. You get
> like a front end with my hosting space (CpanelX) and in there I've created
> user "admin" password "admin" but I cannot seem to login.

I don't know whether the best place for this question is a newsgroup
about PHP or MySQL, but thius group is about Microsoft SQL Server, and your
chances to get help are not fantastic.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Ah, again apologies for my ignorance, I wasn't aware there was a
differance...!

the admin thing was just a test login, but couldn't get it to work. I've
spotted a mysql newsgroup which I will post in...

Many thanks for the help.

"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:6OZLf.3901$5M6.2416@.newsread2.news.atl.earthl ink.net...
> "gjb" <Kookookaachoo@.hotmail.com> wrote in message
> news:CkZLf.26271$wl.7873@.text.news.blueyonder.co.u k...
>> Hi,
>>
>> Apologies if this sounds dumb but I'm very new to this.
>>
>> I'm just trying to create a simple login page (
>> http://aarkenuk.co.uk/barnesg/login.php) In my MySQL databases I have the
>> correct database selected, but it's the users I'm struggling with. You
>> get
>> like a front end with my hosting space (CpanelX) and in there I've
>> created
>> user "admin" password "admin" but I cannot seem to login.
>>
>
> This is a Microsoft SQL Server group, not MySQL group so you're probably
> not
> going to find as much help here as you'd ilke.
>
> However, I would say taht you probably don't want an admin being able to
> access your database from a webpage simply for security reasons.
>
>> This is what I see in the front end..
>>
>> Users in test
>> barnes_admin (Privileges: ALL PRIVILEGES)
>>
>> Connection Strings
>> Perl $dbh =
>> DBI->connect("DBI:mysql:barnes_test:localhost","barnes_admin","<PASSWORD
>> HERE>");
>> PHP $dbh=mysql_connect ("localhost", "barnes_admin", "<PASSWORD
>> HERE>") or die ('I cannot connect to the database because: ' .
>> mysql_error());
>> mysql_select_db ("barnes_test");
>>
>>
>>
>> Is there anything more I need to do? Do you login with barnes_admin or
> just
>> admin? (I've tried both) and why does it created barnes_admin and not
>> just
>> admin? Also what are the connection strings for? do I need to do anything
>> with these?
>>
>> Thanks very much in advance for any advice..
>>
>> Gary
>>
>>
>>|||I'd learn about the differences between the two first! Its useful to know
the advantages and disadvantages of both.

Cheers, Ash

"gjb" <Kookookaachoo@.hotmail.com> wrote in message
news:4SZLf.26282$wl.20042@.text.news.blueyonder.co. uk...
> Ah, again apologies for my ignorance, I wasn't aware there was a
> differance...!
> the admin thing was just a test login, but couldn't get it to work. I've
> spotted a mysql newsgroup which I will post in...
> Many thanks for the help.
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message news:6OZLf.3901$5M6.2416@.newsread2.news.atl.earthl ink.net...
>>
>> "gjb" <Kookookaachoo@.hotmail.com> wrote in message
>> news:CkZLf.26271$wl.7873@.text.news.blueyonder.co.u k...
>>> Hi,
>>>
>>> Apologies if this sounds dumb but I'm very new to this.
>>>
>>> I'm just trying to create a simple login page (
>>> http://aarkenuk.co.uk/barnesg/login.php) In my MySQL databases I have
>>> the
>>> correct database selected, but it's the users I'm struggling with. You
>>> get
>>> like a front end with my hosting space (CpanelX) and in there I've
>>> created
>>> user "admin" password "admin" but I cannot seem to login.
>>>
>>
>>
>> This is a Microsoft SQL Server group, not MySQL group so you're probably
>> not
>> going to find as much help here as you'd ilke.
>>
>>
>> However, I would say taht you probably don't want an admin being able to
>> access your database from a webpage simply for security reasons.
>>
>>
>>> This is what I see in the front end..
>>>
>>> Users in test
>>> barnes_admin (Privileges: ALL PRIVILEGES)
>>>
>>> Connection Strings
>>> Perl $dbh =
>>> DBI->connect("DBI:mysql:barnes_test:localhost","barnes_admin","<PASSWORD
>>> HERE>");
>>> PHP $dbh=mysql_connect ("localhost", "barnes_admin", "<PASSWORD
>>> HERE>") or die ('I cannot connect to the database because: ' .
>>> mysql_error());
>>> mysql_select_db ("barnes_test");
>>>
>>>
>>>
>>> Is there anything more I need to do? Do you login with barnes_admin or
>> just
>>> admin? (I've tried both) and why does it created barnes_admin and not
>>> just
>>> admin? Also what are the connection strings for? do I need to do
>>> anything
>>> with these?
>>>
>>> Thanks very much in advance for any advice..
>>>
>>> Gary
>>>
>>>
>>>
>>
>>

ADO.NET connection to SQL fails

Hello,
I'm putting together an ASP.NET web form (using VB.NET) and the DB I'm trying to do an insert to can't validate my login. I've verified that the account does have permissions to access the SQL DB and that everything is granted as far as the INSERT, UPDATE
, etc...
I have my SQL Server (SQL2K) set up for mixed authentication (both SQL and Windows).
I've tried all the suggestions from the "connectionstrings.com" website and I'm still getting errors stating that the login failed.
Here is a copy of the error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
The above error is happening when I use the connection string of:
"server=MyServer;Initial Catalog=MyDatabase;Integrated Security=TRUE"
I get the same thing when I use "Integrated Security=SSPI" as well.
Here is the error I get when I try to use a user id:
Login failed for user '{user name}'.
The funny thing about it is that the user name specified above is the DBO and it is still rejected.
One last question; have you ever wanted to give up with computers and go back to pen and paper?
Any futher suggestions would be really great! I really appreciate it...
Dale
DBO is not a login, it is a user.
Try connecting with sa (and the sa password). I am guessing that you =
will have better results.
NOTE: You should probably create a login that you will use to connect to =
the database from your web app. If you are planning on using stored =
procedures (a good idea, by the way) they will not need any permissions =
in the database (other than "execute" on the stored procedures used by =
your app).
--=20
Keith
"Dale" <anonymous@.discussions.microsoft.com> wrote in message =
news:1025EFC0-546F-4F76-96CD-75B12AA30E03@.microsoft.com...
> Hello,=20
>=20
> I'm putting together an ASP.NET web form (using VB.NET) and the DB I'm =
trying to do an insert to can't validate my login. I've verified that =
the account does have permissions to access the SQL DB and that =
everything is granted as far as the INSERT, UPDATE, etc...=20
>=20
> I have my SQL Server (SQL2K) set up for mixed authentication (both SQL =
and Windows).=20
>=20
> I've tried all the suggestions from the "connectionstrings.com" =
website and I'm still getting errors stating that the login failed.=20
>=20
> Here is a copy of the error:=20
> Login failed for user '(null)'. Reason: Not associated with a trusted =
SQL Server connection.=20
>=20
> The above error is happening when I use the connection string of:=20
> "server=3DMyServer;Initial Catalog=3DMyDatabase;Integrated =
Security=3DTRUE"=20
>=20
> I get the same thing when I use "Integrated Security=3DSSPI" as well.=20
>=20
> Here is the error I get when I try to use a user id:=20
> Login failed for user '{user name}'.=20
>=20
> The funny thing about it is that the user name specified above is the =
DBO and it is still rejected.=20
>=20
> One last question; have you ever wanted to give up with computers and =
go back to pen and paper? =20
>=20
> Any futher suggestions would be really great! I really appreciate =
it...=20
>=20
> Dale
|||The login failed for user NULL indicates that the account that is
attempting to make the connection is unknown to SQL Server. Look at the IIS
configuration to verify that the user that IIS is using has a login at the
SQL Server. If you are using anonymous access and the IIS machine is on a
separate machine the NT authentication will generate the Login failed for
user NULL.
I would look at articles:
PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"
http://support.microsoft.com/?id=307002
INF: Authentication Methods for Connections to SQL Server in Active Server
Pages
http://support.microsoft.com/?id=247931
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||The problem you are having may be related to how you've configured
your asp.net application. The app may in fact be attempting to connect
using the aspnet process model account unless you've configured IIS to
use impersonation. There's a pretty good "asp.net security best
practices" whitepaper that bears reading:
http://www.microsoft.com/downloads/r...eleaseID=44047
Your machine.config file has the settings you are using in the
<processModel> section -- the default is to have userName="machine",
which means that the aspnet windows account is being used.
In the meantime, try enabling the aspnet windows login in SQLS and
give it the necessary database access. This should work with the
integrated security=sspi setting in your connection string.
--Mary
On Fri, 16 Apr 2004 10:06:03 -0700, "Dale"
<anonymous@.discussions.microsoft.com> wrote:

>Hello,
>I'm putting together an ASP.NET web form (using VB.NET) and the DB I'm trying to do an insert to can't validate my login. I've verified that the account does have permissions to access the SQL DB and that everything is granted as far as the INSERT, UPDAT
E, etc...
>I have my SQL Server (SQL2K) set up for mixed authentication (both SQL and Windows).
>I've tried all the suggestions from the "connectionstrings.com" website and I'm still getting errors stating that the login failed.
>Here is a copy of the error:
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
>The above error is happening when I use the connection string of:
>"server=MyServer;Initial Catalog=MyDatabase;Integrated Security=TRUE"
>I get the same thing when I use "Integrated Security=SSPI" as well.
>Here is the error I get when I try to use a user id:
>Login failed for user '{user name}'.
>The funny thing about it is that the user name specified above is the DBO and it is still rejected.
>One last question; have you ever wanted to give up with computers and go back to pen and paper?
>Any futher suggestions would be really great! I really appreciate it...
>Dale

ADO.NET connection to SQL fails

Hello,
I'm putting together an ASP.NET web form (using VB.NET) and the DB I'm tryin
g to do an insert to can't validate my login. I've verified that the account
does have permissions to access the SQL DB and that everything is granted a
s far as the INSERT, UPDATE
, etc...
I have my SQL Server (SQL2K) set up for mixed authentication (both SQL and W
indows).
I've tried all the suggestions from the "connectionstrings.com" website and
I'm still getting errors stating that the login failed.
Here is a copy of the error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Se
rver connection.
The above error is happening when I use the connection string of:
"server=MyServer;Initial Catalog=MyDatabase;Integrated Security=TRUE"
I get the same thing when I use "Integrated Security=SSPI" as well.
Here is the error I get when I try to use a user id:
Login failed for user '{user name}'.
The funny thing about it is that the user name specified above is the DBO an
d it is still rejected.
One last question; have you ever wanted to give up with computers and go bac
k to pen and paper?
Any futher suggestions would be really great! I really appreciate it...
DaleDBO is not a login, it is a user.
Try connecting with sa (and the sa password). I am guessing that you =
will have better results.
NOTE: You should probably create a login that you will use to connect to =
the database from your web app. If you are planning on using stored =
procedures (a good idea, by the way) they will not need any permissions =
in the database (other than "execute" on the stored procedures used by =
your app).
--=20
Keith
"Dale" <anonymous@.discussions.microsoft.com> wrote in message =
news:1025EFC0-546F-4F76-96CD-75B12AA30E03@.microsoft.com...
> Hello,=20
>=20
> I'm putting together an ASP.NET web form (using VB.NET) and the DB I'm =
trying to do an insert to can't validate my login. I've verified that =
the account does have permissions to access the SQL DB and that =
everything is granted as far as the INSERT, UPDATE, etc...=20
>=20
> I have my SQL Server (SQL2K) set up for mixed authentication (both SQL =
and Windows).=20
>=20
> I've tried all the suggestions from the "connectionstrings.com" =
website and I'm still getting errors stating that the login failed.=20
>=20
> Here is a copy of the error:=20
> Login failed for user '(null)'. Reason: Not associated with a trusted =
SQL Server connection.=20
>=20
> The above error is happening when I use the connection string of:=20
> "server=3DMyServer;Initial Catalog=3DMyDatabase;Integrated =
Security=3DTRUE"=20
>=20
> I get the same thing when I use "Integrated Security=3DSSPI" as well.=20
>=20
> Here is the error I get when I try to use a user id:=20
> Login failed for user '{user name}'.=20
>=20
> The funny thing about it is that the user name specified above is the =
DBO and it is still rejected.=20
>=20
> One last question; have you ever wanted to give up with computers and =
go back to pen and paper? =20
>=20
> Any futher suggestions would be really great! I really appreciate =
it...=20
>=20
> Dale|||The login failed for user NULL indicates that the account that is
attempting to make the connection is unknown to SQL Server. Look at the IIS
configuration to verify that the user that IIS is using has a login at the
SQL Server. If you are using anonymous access and the IIS machine is on a
separate machine the NT authentication will generate the Login failed for
user NULL.
I would look at articles:
PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"
http://support.microsoft.com/?id=307002
INF: Authentication Methods for Connections to SQL Server in Active Server
Pages
http://support.microsoft.com/?id=247931
Rand
This posting is provided "as is" with no warranties and confers no rights.|||The problem you are having may be related to how you've configured
your asp.net application. The app may in fact be attempting to connect
using the aspnet process model account unless you've configured IIS to
use impersonation. There's a pretty good "asp.net security best
practices" whitepaper that bears reading:
http://www.microsoft.com/downloads/...ReleaseID=44047
Your machine.config file has the settings you are using in the
<processModel> section -- the default is to have userName="machine",
which means that the aspnet windows account is being used.
In the meantime, try enabling the aspnet windows login in SQLS and
give it the necessary database access. This should work with the
integrated security=sspi setting in your connection string.
--Mary
On Fri, 16 Apr 2004 10:06:03 -0700, "Dale"
<anonymous@.discussions.microsoft.com> wrote:

>Hello,
>I'm putting together an ASP.NET web form (using VB.NET) and the DB I'm trying to do
an insert to can't validate my login. I've verified that the account does have perm
issions to access the SQL DB and that everything is granted as far as the INSERT, UP
DAT
E, etc...
>I have my SQL Server (SQL2K) set up for mixed authentication (both SQL and
Windows).
>I've tried all the suggestions from the "connectionstrings.com" website and
I'm still getting errors stating that the login failed.
>Here is a copy of the error:
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL S
erver connection.
>The above error is happening when I use the connection string of:
>"server=MyServer;Initial Catalog=MyDatabase;Integrated Security=TRUE"
>I get the same thing when I use "Integrated Security=SSPI" as well.
>Here is the error I get when I try to use a user id:
>Login failed for user '{user name}'.
>The funny thing about it is that the user name specified above is the DBO a
nd it is still rejected.
>One last question; have you ever wanted to give up with computers and go ba
ck to pen and paper?
>Any futher suggestions would be really great! I really appreciate it...
>Dale

ADO Integrated Security Pass Through Again

The previous thread died so I'm sorry for the repost.
I am working on making my application inherit the workstation login user
information so that users aren't presented with multiple logins.
Does anyone have any experience linking internal application user management
(ie: USERS table) with windows authentication?
I have access rights that a specific to my application such as menu
options, reports, specific actions, etc. The application was developed 8
years ago and supported multiple database platforms. We have moved to only
supporting MS SQL Server 7, 2000 and 2005.
What's the best way to link these together since DBAs wouldn't be able to
assign my application specific access rights via MS SQL Server Management
Studio/Enterprise Manager?
Any comments or suggestions would be great.Hi!
First, your application should use ADO connection string like
"SERVER=mymssql; Integrated Security=SSPI;"
thus application will connect to SQL with current logged user
credentials. Naturally, user must have some rights on SQL server.
You can set those right for NT group, not for individual user accounts.
The user account name is accessible in t-sql and you can build some
additional logic:
CREATE PROC GetCustomUserRights
AS
declare @.NT_login varchar(64)
set @.NT_login = SYSTEM_USER
select UserRightName,UserRightValue from USERS where UserName = @.NT_login
RETURN 0
GO
implying the table USERS has structure and data like:
UserName, UserRightName, UserRightValue
"ACME\user1", "AdvancedMenu", "True"
"ACME\user2", "AdvancedMenu ", "False"
...
Best regards, Anatoli
"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote

> The previous thread died so I'm sorry for the repost.
> I am working on making my application inherit the workstation login user
> information so that users aren't presented with multiple logins.
> Does anyone have any experience linking internal application user
> management
> (ie: USERS table) with windows authentication?
> I have access rights that a specific to my application such as menu
> options, reports, specific actions, etc. The application was developed 8
> years ago and supported multiple database platforms. We have moved to only
> supporting MS SQL Server 7, 2000 and 2005.
> What's the best way to link these together since DBAs wouldn't be able to
> assign my application specific access rights via MS SQL Server Management
> Studio/Enterprise Manager?
> Any comments or suggestions would be great.
>|||"Anatoli Dontsov" <Anatoli@.dontsov.com> wrote in message
news:eXg$wQOvGHA.4296@.TK2MSFTNGP06.phx.gbl...
> Hi!
> First, your application should use ADO connection string like
> "SERVER=mymssql; Integrated Security=SSPI;"
> thus application will connect to SQL with current logged user
> credentials. Naturally, user must have some rights on SQL server.
> You can set those right for NT group, not for individual user accounts.
> The user account name is accessible in t-sql and you can build some
> additional logic:
> CREATE PROC GetCustomUserRights
> AS
> declare @.NT_login varchar(64)
> set @.NT_login = SYSTEM_USER
> select UserRightName,UserRightValue from USERS where UserName = @.NT_login
> RETURN 0
> GO
> implying the table USERS has structure and data like:
> UserName, UserRightName, UserRightValue
> "ACME\user1", "AdvancedMenu", "True"
> "ACME\user2", "AdvancedMenu ", "False"
> ...
Thanks. Has anyone had any experience creating the list of users for the
access rights? For example: a user logs in and I check their access rights,
is the best solution to have admin type in the NT login name into my app and
add access rights? Or can I provide a dropdown of users based in some
network query?

ADO Integrated Security Pass Through Again

The previous thread died so I'm sorry for the repost.
I am working on making my application inherit the workstation login user
information so that users aren't presented with multiple logins.
Does anyone have any experience linking internal application user management
(ie: USERS table) with windows authentication?
I have access rights that a specific to my application such as menu
options, reports, specific actions, etc. The application was developed 8
years ago and supported multiple database platforms. We have moved to only
supporting MS SQL Server 7, 2000 and 2005.
What's the best way to link these together since DBAs wouldn't be able to
assign my application specific access rights via MS SQL Server Management
Studio/Enterprise Manager?
Any comments or suggestions would be great.Hi!
First, your application should use ADO connection string like
"SERVER=mymssql; Integrated Security=SSPI;"
thus application will connect to SQL with current logged user
credentials. Naturally, user must have some rights on SQL server.
You can set those right for NT group, not for individual user accounts.
The user account name is accessible in t-sql and you can build some
additional logic:
CREATE PROC GetCustomUserRights
AS
declare @.NT_login varchar(64)
set @.NT_login = SYSTEM_USER
select UserRightName,UserRightValue from USERS where UserName = @.NT_login
RETURN 0
GO
implying the table USERS has structure and data like:
UserName, UserRightName, UserRightValue
"ACME\user1", "AdvancedMenu", "True"
"ACME\user2", "AdvancedMenu ", "False"
...
Best regards, Anatoli
"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote
> The previous thread died so I'm sorry for the repost.
> I am working on making my application inherit the workstation login user
> information so that users aren't presented with multiple logins.
> Does anyone have any experience linking internal application user
> management
> (ie: USERS table) with windows authentication?
> I have access rights that a specific to my application such as menu
> options, reports, specific actions, etc. The application was developed 8
> years ago and supported multiple database platforms. We have moved to only
> supporting MS SQL Server 7, 2000 and 2005.
> What's the best way to link these together since DBAs wouldn't be able to
> assign my application specific access rights via MS SQL Server Management
> Studio/Enterprise Manager?
> Any comments or suggestions would be great.
>|||"Anatoli Dontsov" <Anatoli@.dontsov.com> wrote in message
news:eXg$wQOvGHA.4296@.TK2MSFTNGP06.phx.gbl...
> Hi!
> First, your application should use ADO connection string like
> "SERVER=mymssql; Integrated Security=SSPI;"
> thus application will connect to SQL with current logged user
> credentials. Naturally, user must have some rights on SQL server.
> You can set those right for NT group, not for individual user accounts.
> The user account name is accessible in t-sql and you can build some
> additional logic:
> CREATE PROC GetCustomUserRights
> AS
> declare @.NT_login varchar(64)
> set @.NT_login = SYSTEM_USER
> select UserRightName,UserRightValue from USERS where UserName = @.NT_login
> RETURN 0
> GO
> implying the table USERS has structure and data like:
> UserName, UserRightName, UserRightValue
> "ACME\user1", "AdvancedMenu", "True"
> "ACME\user2", "AdvancedMenu ", "False"
> ...
Thanks. Has anyone had any experience creating the list of users for the
access rights? For example: a user logs in and I check their access rights,
is the best solution to have admin type in the NT login name into my app and
add access rights? Or can I provide a dropdown of users based in some
network query?

ADO Integrated Security Pass Through

I am working on making my application inherit the workstation login user
information so that users aren't presented with multiple logins.
Is it safe enough to use Integrated Security via the connection string. If
that succeeds, read the windows user name and check that against an internal
username?
Does anyone have any experience linking internal application user management
(ie: USERS table) with windows authentication?
Any comments or suggestions would be great.First key point: By using Windows authentication, you do NOT have to have a
USERS table. In SQL Server, you assign all permissions to the Windows login
or the Windows network group. (It makes life so much easier for the DBA.)
Windows Integrated Security (for SQL 2000) is far superior to SQL
authentication, and far better than trying to keep a USERS table up to date.
In SQL Server, use the SYSTEM_USER system function to retrieve the users
login name (in the form of [domain\username].)
Example:
SELECT SYSTEM_USER
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
news:uJVfx3ntGHA.2392@.TK2MSFTNGP05.phx.gbl...
>I am working on making my application inherit the workstation login user
>information so that users aren't presented with multiple logins.
> Is it safe enough to use Integrated Security via the connection string. If
> that succeeds, read the windows user name and check that against an
> internal username?
> Does anyone have any experience linking internal application user
> management (ie: USERS table) with windows authentication?
> Any comments or suggestions would be great.
>|||"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23Mmz2potGHA.324@.TK2MSFTNGP06.phx.gbl...
> First key point: By using Windows authentication, you do NOT have to have
> a USERS table. In SQL Server, you assign all permissions to the Windows
> login or the Windows network group. (It makes life so much easier for the
> DBA.)
> Windows Integrated Security (for SQL 2000) is far superior to SQL
> authentication, and far better than trying to keep a USERS table up to
> date.
> In SQL Server, use the SYSTEM_USER system function to retrieve the users
> login name (in the form of [domain\username].)
> Example:
> SELECT SYSTEM_USER
> --
Thanks Arnie. That call is very helpful.
However, I have access rights that a specific to my application such as menu
options, reports, specific actions, etc. The application was developed 8
years ago and supported multiple database platforms. We have moved to only
supporting MS SQL Server 7, 2000 and 2005.
What's the best way to link these together since DBAs wouldn't be able to
assign my application specific access rights via MS SQL Server Management
Studio/Enterprise Manager?

ADO Integrated Security Pass Through

I am working on making my application inherit the workstation login user
information so that users aren't presented with multiple logins.
Is it safe enough to use Integrated Security via the connection string. If
that succeeds, read the windows user name and check that against an internal
username?
Does anyone have any experience linking internal application user management
(ie: USERS table) with windows authentication?
Any comments or suggestions would be great.First key point: By using Windows authentication, you do NOT have to have a
USERS table. In SQL Server, you assign all permissions to the Windows login
or the Windows network group. (It makes life so much easier for the DBA.)
Windows Integrated Security (for SQL 2000) is far superior to SQL
authentication, and far better than trying to keep a USERS table up to date.
In SQL Server, use the SYSTEM_USER system function to retrieve the users
login name (in the form of [domain\username].)
Example:
SELECT SYSTEM_USER
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
news:uJVfx3ntGHA.2392@.TK2MSFTNGP05.phx.gbl...
>I am working on making my application inherit the workstation login user
>information so that users aren't presented with multiple logins.
> Is it safe enough to use Integrated Security via the connection string. If
> that succeeds, read the windows user name and check that against an
> internal username?
> Does anyone have any experience linking internal application user
> management (ie: USERS table) with windows authentication?
> Any comments or suggestions would be great.
>|||"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23Mmz2potGHA.324@.TK2MSFTNGP06.phx.gbl...
> First key point: By using Windows authentication, you do NOT have to have
> a USERS table. In SQL Server, you assign all permissions to the Windows
> login or the Windows network group. (It makes life so much easier for the
> DBA.)
> Windows Integrated Security (for SQL 2000) is far superior to SQL
> authentication, and far better than trying to keep a USERS table up to
> date.
> In SQL Server, use the SYSTEM_USER system function to retrieve the users
> login name (in the form of [domain\username].)
> Example:
> SELECT SYSTEM_USER
> --
Thanks Arnie. That call is very helpful.
However, I have access rights that a specific to my application such as menu
options, reports, specific actions, etc. The application was developed 8
years ago and supported multiple database platforms. We have moved to only
supporting MS SQL Server 7, 2000 and 2005.
What's the best way to link these together since DBAs wouldn't be able to
assign my application specific access rights via MS SQL Server Management
Studio/Enterprise Manager?

ADO Error Code:0x80040e4d

Hello all,

I use Crystal Report v9, SQL server 2000.
When I try to connect to a Database via ADO, I got the following error.

Login failed.
Details :ADO Error Code:0x80040e4d
Source:Microsoft OLE DB Provider for SQL Server
Description:Login failed for usexxxxxxx
SQL State: 42000
Native Error:18456

Is there anyone how has this problem?
How can I fix this?

Thanks in advance,
Do.

--
Message posted via http://www.sqlmonster.com"Do Park via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
news:9caa7e6d6eff41c1984f7334221dc753@.SQLMonster.c om...
> Hello all,
>
> I use Crystal Report v9, SQL server 2000.
> When I try to connect to a Database via ADO, I got the following error.
> Login failed.
> Details :ADO Error Code:0x80040e4d
> Source:Microsoft OLE DB Provider for SQL Server
> Description:Login failed for use'xxxxxxx'
> SQL State: 42000
> Native Error:18456
> Is there anyone how has this problem?
> How can I fix this?
> Thanks in advance,
> Do.
> --
> Message posted via http://www.sqlmonster.com

"Login failed" suggests that you need to check the login you're using to
connect with - is it a SQL login, or a Windows account; are you using a DSN
or a connection string; can you connect from osql.exe or Query Analyzer
using the same account (or another account) etc.

Simon|||I use Windows authentication. I can access other databases via the same way
(Crystal Report). I connected this database via ADO successfully two or
three days ago. There was no change in my environment and SQL Server.

Best regards,
Do.

--
Message posted via http://www.sqlmonster.com|||Do Park via SQLMonster.com (forum@.SQLMonster.com) writes:
> I use Windows authentication. I can access other databases via the same
> way (Crystal Report). I connected this database via ADO successfully two
> or three days ago. There was no change in my environment and SQL
> Server.

Probably there was. Unfortunately, it is impossible for us who don't
have access to your environment to tell what is going on. You will
have to see your local admin to sort it out.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Admin sql login

Hi all,
If I want to create Amin user in SQL and give that user all permissions like
sa login.
How would I do that without having to go into each database and creating
roles
or checking permissions for each task?
thanks
GVYou can add the user to the sysadmin fixed server role.
-Sue
On Fri, 11 Feb 2005 17:22:25 -0500, "gv" <viatorg@.musc.edu>
wrote:

>Hi all,
>If I want to create Amin user in SQL and give that user all permissions lik
e
>sa login.
>How would I do that without having to go into each database and creating
>roles
>or checking permissions for each task?
>thanks
>GV
>|||Thanks
GV
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:q6lq01d8hitujnvbqovus510hfgqo6m00k@.
4ax.com...
> You can add the user to the sysadmin fixed server role.
> -Sue
> On Fri, 11 Feb 2005 17:22:25 -0500, "gv" <viatorg@.musc.edu>
> wrote:
>
>