I am having a problem with NT trusted connections. I am running a front-end from Access 97 with linked tables to an SQL Server. Whenever I open a form, I will be prompted for login. Since I am already on an NT domain, I make use of 'trusted connection'. However, whenever the form is refreshed or a requery is sent, I am always prompted for login again. Using an SQL user login does not give me the problem and it's a one time login.
Q : How do I configure SQL such that it doesn't prompt me for login everytime whenever I choose 'trusted connection' ?
I folks.I Have installed sql server 2005 express and choosed windowsauthentication on instalation, but i make a mistake and now i needmixed authentication, how can i modify this whithout uninstall andinstall again the application?thanks for the help.
Hi there,I have installed MS SQL Server 2005 on my machine with windows authentication. But now I want to switch the authentication mode to SQL Authentication. I am unable to switch, I can’t find the proper way to do so here in 2005.Could any one help me in doing this?Thank you,-Ahsan
(Using win2k, sqlserver2k, framework 1.1) I have an fairly data-heavy application that uses Windows authentication (Trusted connection/aspnet account) to connect to Sql Server. The site uses IIS basic authentication.
On the dev server everything works fine but when I move to the live server things get strange and it starts to crawl along. (Pages load OK but then it just crawls as it loads the datagrids etc. Sometimes it brings back incomplete/incorrect data )
BUT When I use Sql Authentication to connect to Sql Server and there is no problem at all!
Ok, there is something obviously wrong with the live server (which is identical setup to dev)but I dont know where to start.
I've got two applications which both have a database on my MS SQL 2000 server. The problem is, one application must use Windows Integrated Authentication (which it is currently using and cannot be changed) whilst the other application which I'm trying to configure must use a SQL password.
Since the server has already been configured to use Windows Integrated Authentication for the existing database and application, how do I configure the other database to use the SQL password?
My work is using a shared application which accesses a MSSQL 2000 database. To access the application, the folder on the Windows 2003 Server is shared and users can access the folder through a shared drive.
For the application to access the database, it uses an ODBC connection to the MSSQL server which originally used the SA password.
We have recently switched to using Windows Integrated Authentication because we believe it offers a higher level of security. However the only way in which we have been able to enable this is to add the windows users to the SQL server.
The problem with this is that the application sets permissions for individual users on what records they can see within the database. We have found that by adding the windows users to the SQL Server, they can bypass the permissions the set by the application by simply using any application that can use an ODBC connection, such as Enterprise Manager, and see all the database.
One way around this would be to set up domains of users with access privileges to the tables which reflect the permissions set by the application, and configuring a view of the data so they may only see the records that they have permissions to. However to do this would require a high administrative cost to ensure that changes made in the application are reflected in the privileges of the SQL server.
Instead, is there a way the SQL server can authenticate that the ODBC connection is coming from the correct application using Windows Integrated Authentication?
This would allow the applcation to determine security, and stop users from connecting to the SQL server using other applications.
Alternatively, can the SQL server, using Windows Integrated Authentication, also ask the application to supply a username and password?
Any help with this matter would be greatly appreciated.
Hi,I'm using SQL Server 2005. My Connection String looks like that at the moment: <add name="LocalSqlServer" connectionString="Data Source=xx;Initial Catalog=xx;Persist Security Info=True;User ID=xx;Password=xx" providerName="System.Data.SqlClient"/> Now I'd like to change this kind of authentication to Integrated Windows AuthenticationI added the WorkerProcess IIS_WPG to the permitted Users but it didn't help.Changed the Connection String to this:connectionString="Server=xx;Database=xx;Trusted_Connection=True;"All I'm getting is that my NetworkService is not permitted to access DB when I try to connect to the DB in ASP.NET.How can I properly configure that? Thanks!
Say, I have configured my SQL to use Mixed Authentication. Now, I have a applicaiton which uses my SQL Server. The application just creates a database in SQL Server and uses the database to store its information.
This application also has a SYSTEM DSN under ODBC through which it accesses the database. For the application to access this database, should I only use SA (as my SQL instance is configured to use Mixed Authentication) or can I use Windows Authentcation too...
If I should only use SA, do we have a documentation which talks about this.
For using different services of SQL SERVER 2005 which is better... Windows Authentication or SQL Server Authentication? what are the advantages and disadvantages of both?
I wonder if it is possible to set forms authentication for report manager but leave report server "as it is". I need to authenticate users from external LDAP and can't use windows authentication for report manager, but I would also like to leave report server open for anonymous users. In that way authenticated administrators could create reports which anonymous users could read.
I tested the Security Extension Sample and got it working when I rewrote the authentication part with my own LDAP authentication.
If I have understood correctly, the report manager is just application inside report server so is it possible to use forms authentication with one application but still leave the report server with Windows authentication?
I need to figure out what kind of Authentication , I need to use for following applicaiton
Product : -
1 ) It resides on a its Domain and has access to Database on that Domain. 2 ) We have a application level login , n based on application login id display specific pages.
The question that bother me is this
Q ) If i use NT authentication , then a user will be required to
a ) Login to domain (with userid and password) first and then
b ) Then i would require to again login to applicaiton with application level login and password.(different levels of login as there) Based on the application level login i will display only specific asp pages. They have different access rights..and roles.
Requirment is to login only once..and it should authenticate to application display specific pages and authenticate to SQl server database also..
Is there any way thru which i can map my application level login to SQl server.. and what authentication should i use..
I am in the process of rolling out a sql server 2005 enterprise install and had a question regarding authentication. We will be providing sql hosting for a number of groups on our campus, many who are not using our campus-wide active directory, though they all have an AD account.
Windows authentication via the management studio appears to use your AD authentication tokens and will not allow them to enter a username/password combo. Is there any way to configure this?
I would like to use our campus AD for obvious reasons but if there is a requirement for passing tokens this isn't going to work right? It's also going to make database mirroring more of a challenge.
Hi all, My SQL Server 7.0 is now running in a mixed mode authentication. I understand that this method of authentication is not safe. So, Ive planned to change my server's method of authentication from mixed to NT-only mode. Kindly tell me what are the points I should consider for doing this, so that, the existing data and the users are not affected.
We recently moved our SQL Server services to a dedicated machine, and things have gone relatively smoothly.
My boss's major concern is that now when he runs some scripts in another application that updates sales data with the newest info from the database, it pops up a login box with the correct information in it already, but they have to hit OK to finish running the script. This was not happening on the old server. I've double-checked the ODBC data sources are correct, and have compared the security for the 2 servers and they appear to be identical still. Has anyone seen this before or knows what I'm doing wrong?
My sql server is configured for W NT security.Whenever I am running from program from VB6, & the user name is prompted for, even if I enter a user that is not defined as an NT user, SQL lets it connect to the database. WHY? Thanks n advance! Adie
I am reviewing the requirements for NT Authentication for SQL Server 7.0. I want to take advantage of window NT user security. I also want just a single security point. My question is that I can make several NT groups for various users (DBA, development, accounting, finance, sales, etc.) but how are SQL Server roles, permissions, and passwords applied to these NT groups? There are no groups in 7.0, right?
We're having a small problem with our Authentication on SQL. We set SQL up to use NT Authentication only. We then created a group on the NT Server and gave it the necessary permissions to make changes to the MSSQL7DATA directory on the SQL Server. Next we created the NT Logins on SQL. We're using Access 97 & ODBC to connect to SQL. Problem is that the first time the users open an Access 97 table, they get a prompt asking for an SQL Username/Password, or a checkbox option to use NT Authentication. I've just been having them click the "Use Trusted Connection." Is there a way to force NT Authentication and avoid having that popup box show each time Access is opened? I'd like it so that the user does not see any boxes when they open the table. I have a feeling we've left something out on the SQL side. Thanks for any help you can provide.
Hi there, Is there any sp or xp which can help me out to change the sql server authentication mode to 'SQL Server and Windows' . I need to do this from only through a sql script. Thanks Paul
How is it possible to use NT authentication in 'WORKGROUP' environment. I have my SQL server in one workgroup. And I want to access this server from a workstation which is in another workgroup. I am able to do this by using SQL authentication and passing the username and password. How can I do the same, with NT authentication? Regards Chakri
I have 2 instance on SQL Server, One remote the other local. Both authenticate via window NT. How can I change one or both? To connect to a application do I setup a usergroup? Grranted this is still in the testing stages.
Dear everyone, Me agains, i have a problems in my sql server 2005 Authentication cant anyone tell me how to set the SQL authentication for server 2005?
i use the following coding for connection but it cant log to my sql server...
Hello everyone. I made a reports in SQL authentication. Is it possible to hide the credentials(asking for username and password) when i generate a report? Pls help.
Hi everyone. Whay is the difference of Windows, SQL, and Form authentication to each other? Correct me if Im wrong, Windows Authentication is running through your local machine. SQL authentication is for the server. I don't know what is meant by Form Authentication. Am I right?
Hello All,i was wondering what is the main difference between the windowsauthentication and mixed mode authentication??according to security recommendations, we should enable windowsauthentication, rather than mixed one, i don get the point why do werefuse the mixed mode authentication, although it includes windowsauthentication together with an extra layer of defense by the aid of anextra authentication mechanism, sql authentication.i hope i can find out why??if anyone can recommend me some papers or books, i'll be thankfull buti hope it explains from the security point of view.Thanx for time and sorry for interruption
I have deployed a range of reports over a network with Reporting Services 2000 and i am having some issues with users being asked for a Network Login when they go to run the report. The reports are available to users on various Networks, not just the one i am on. Basically, the users on my network breeze through to the report but the users on other Networks get prompted for a username and password. We set up a dummy Network account on my Network and got them to type that username and password in when they were prompted for it and it worked ok.
The only issue is i want them to access the reports without using the username and password
My SQLExpress seems to be set for windows authentication and not sql server authentication ... I am not quite sure why it is set to windows authentication - I installed this with Visual Studio 2005 and it just seemed to be set that way.Am I able to change this - if I choose sql authentication when connecting I get an errorIf someone could answer this point I would be most grateful !!Patrick
Hey there, I have a table [user] in a SQLExpress database [Database.mdf] in the App_Data folder. There are two columns. [userId] and [password]. I want to authenticate the user who wants to log in through a Login control. the user should have his userId and password in the [user] table. I digged and made my code. but it doesn't work it keeps giving me that the user is not authenticated. i guess it has no errors. please tell me if you find the error. here is the code: 1 protected void Login1_Authenticate(object sender, AuthenticateEventArgs e) 2 { 3 SqlConnection conExpress = new SqlConnection("Data Source=.\SQLEXPRESS;Initial Catalog=Database;Integrated Security=True;User Instance=False"); //Create the server connection 4 5 try 6 { 7 string id_user = Login1.UserName.Trim(); //Get the username from the control 8 string pass_user = Login1.Password; //get the Password from the control 9 10 //These are a sql and connection Examples 11 string sql = "SELECT userId, password FROM user WHERE userId = @param_Id AND password = @param_Password"; 12 SqlCommand comSQL = new SqlCommand(sql, conExpress); //Create the sql command using sql string and sql connection 13 14 //Add the sql parameters 15 comSQL.Parameters.AddWithValue("@param_Id", id_user); //New on VS 2.0 16 comSQL.Parameters.AddWithValue("@param_Password", pass_user); 17 18 string cod_user = ""; 19 string name_user = ""; 20 21 //Open database connection 22 conExpress.Open(); 23 SqlDataReader dr = comSQL.ExecuteReader(); 24 while (dr.Read()) 25 { 26 cod_user = dr.GetValue(0).ToString(); //The coduser is unique onto database table 27 name_user = dr.GetValue(1).ToString(); 28 } 29 conExpress.Close();//Close Database Connection 30 if (cod_user != "") //The user exist onto database 31 { 32 //Create the session vars 33 Session["coduser"] = cod_user; 34 Session["nameuser"] = name_user; 35 e.Authenticated = true; //Grant the access, Goes to DestinationPageUrl 36 } 37 } 38 catch(Exception)//On Login Error 39 { 40 e.Authenticated = false;//Confirm that you are out 41 conExpress.Close();//On any error case, close the database connection 42 } 43 }
