I would like to add a new data source to my windows application using SQL server authentication. When I made the connection it did not have any problem. When I add the tableAdapter control it give me the message:
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 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.
I was trying to transfer a SQL Server 2000 database to SQL Server 2005 using SQL Server Objects Task. However, The following error message was encountered: "[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".€œ
I have created an EndPoint in SQL Server 2005 as per the code below.
CREATE ENDPOINT OSTC_LMS_Endpoint
AUTHORIZATION LMSEndPointUsers
STATE = STARTED
AS HTTP(
PATH = '/ostc_sql_endpoint',
AUTHENTICATION = (BASIC),
PORTS = (SSL),
SITE = 'OSTC-DEV-001'
)
FOR SOAP (
WEBMETHOD 'ostc_SQLSoapTester'
(name='OSTC_LMS_06.dbo.ostc_SQLSoapTester',
FORMAT = ROWSETS_ONLY,
SCHEMA=STANDARD),
WSDL = DEFAULT,
LOGIN_TYPE = MIXED,
SCHEMA = STANDARD,
DATABASE = 'OSTC_LMS_06',
NAMESPACE = 'http://tempUri.org/'
)
GO
USE master
GRANT CONNECT ON ENDPOINT::OSTC_LMS_Endpoint
TO [LMSEndPointUsers]
GO
USE master
GRANT CONNECT ON ENDPOINT::OSTC_LMS_Endpoint
TO [ostc-dev-001endPointUsers]
GO
----------------------------------------------------------------------------------------------------------------- The SPROC being exposed as the webmethod: -
The computer in question is our dev server and is running as a workgroup machine with the following: - Win Server 2003 SQL Server 2005 .net Framework 2.0 No firewalls or Proxies are in the way.
The computer has to be as a workgroup machine to reflect our live server.
The user LMSEndPointUsers is a SQL Server Login The user ostc-dev-001endPointUsers is a machine login
We have employed the Security class as per the information given in the SQL Server documentation with the intention of using the WS-Security headers that apparently are to be used when trying to authenticate using a SQL Server login.
I have 7.0 server running with sp2 on NT box sp 5. This Sql server is configured to take both sql and NT authentication. Somehow, the bridge between NT and SQL server doesn't seem to be working as sql server does not recognize any NT authentication. Is there any way to fix it?
Because of this problem, I am unable to schedule any DTS package as sql server security doesn't recognize the sqlagent startup account and gives a login failure error.
I am about to open a ticket with Microsoft but before that if anybody can suggest me anything..
I have an SQL Server (2000 Edition) that does not belong to a domain; Server A. (It loggs onto its own computer domain). From this server I would like to add another sql server registration through Enterprise Manager that does belong to a domain; Server B (also 2000 Edition).
The only way I can register Server B on the Server A computer is by logging onto the domain that Server B belongs to.
Is it possible to just use SQL Server authentication and not have Server A logon to the Server B domain? If so what could I be doing wrong?
When Server A is logged onto its own local computer domain I can ping Server B and also resolve the server by name.
I can currently log in through Management Studio using Windows Authentication. I want to login using my sa account (which exists) and a password, and eventually be able to do role based security for additional users.
Hi ,am new to sqlserver 2000.I want to connect to my sqlserver which is aremote machine.I want to connect to sqlserver by sqlserverauthentication.Even though i added the available sqlserver in myclient as it shows, it is connected only by windows[nt)authentication.Why it is showing so ?.* But it is connected via Query analyzer in sqlauthentication.I want to connect this sqlserver to my asp.net .Is the connection string as follows is right ,if no pls correct me,---------Persist Security Info=False;IntegratedSecurity=SSPI;database=NORTHWIND;server=IISSERVER; User id=sa"---------It shows the error .Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.I ve'nt mentioned any authentication mechanisym in my query string..From the error it defaultly accepts the NT authentication.How can iover ride this to sql authentication.Pls tell me the procedures should be made to connect to sqlserver insql authentication.Thx & RegardsRaghu
fellas i am a noob to sql server....i am using visual web developer 2005 express..i added a database to my site and created a table until now i have been using windows authentication...the task my teacher gave me was to create a table and then host it on iis..i copied my site to wwwroot folder now when i access it using iexplorer i get this
Server Error in '/' Application.
Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Source Error:
Line 52: ASP.NET to identify an incoming user. Line 53: --> Line 54: <authentication mode="Windows" /> Line 55: <!-- Line 56: The <customErrors> section enables configuration Source File: c:inetpubwwwrootdbtestingweb.config Line: 54
i tried to change the connection type to sql server authentication and use the default(what i know) sa account but i get an error login failed for user 'sa' the user is not associated with trusted SQl server connection. what am i doing wrong? is there a way to create a user for SQL server 2005?...please remember i only have visual web developer 2005 express installed... regards
I am trying to setup cached reports so that one of my larger reports doesn't have to be re-run every time someone wants to view it (the data source only updates every 24 hours).
Anyway I made a new data source, set the report to use that, and in that data source I said to use "SQLexampleUserName" as the stored credentials.
Now when I go to run the report it says: Login failed for user 'username'. The user is not associated with a trusted SQL Server connection.
I have just created some SSIS package. Some package has connection to remote SQL Server 2005 by SQL server authentication mode (not windows).
In the connection property I have setted "save my password", but I have found that after a while the connection is missed and I have to make the Logon. this happen always to random.
Do you know how to keep the connection persistent?
Viual Studio 2003; ASP.Net; .Net Framework 1.1, SQL Server 2000Hi,We have two domains in our network - prod.domain.com and dev.domain.com. There is no trust relationship between the two domains. I am trying to connect to an SQL Server in dev.domain.com using SQL Server Authentication from prod.domain.com. My connection string uses the fully qualified domain name (xxxxxx.dev.domain.com) to connect. The error I receive is SQL Server does not exist or access denied. I can access the database through SQL Query Analyser and SQL Enterprise Manager across the domains with no problems. I can also connect through a .udl file using the same SQL Server Authentication information.If I run my application from dev.domain.com accessing a database that sits in prod.domain.com then the connection is fine.Can someone point me in the direction of any areas I can troubleshoot to see what is preventing the connection please? The only things I can see on the web are details of windows authentication across domains which isn't relevant to me in this instance. I've been pulling what little hair I have out over this for the last week.Thanks in advance.
I am new to the whole ASP .NET scene, so my knowledge is very limited, and if I’m not clear enough please let me know. I am reading a book published by APress about ASP .NET with C# and I am at the point where I get to begin working with data (fun!!). The problem is that I’m not able to connect to the SQL Server. I have Server 2003 and SQL Server 2005 running on a separate machine than the computer that I use for development – the server is named THESERVER, the SQL server is named THESQLSERVER, and the computer I use for development is my laptop named MYLAPTOP. So here’s my connection string (I put this in my web.config XML file):<add name="Pubs" connectionString="DataSource=THESERVERTHESQLSERVER; Initial Catalog=pubs;Integrated Securit=SSPI"/> Now here’s what my book reads: For Windows authentication to work, the currently logged-on Windows user must have the required authorization to access the SQL database. This is all it says about Windows authentication because the book assumes that I am running MS SQL Express off localhost. Questions: Does the book mean that I will have to add a user to my server for my laptop? If so, how do I log into this user using the connection string?What does it mean by “the current logged-on Windows user”? Is that referring to the user on my laptop, or a user on the server? I’ve been reading around trying to find more information on exactly how Windows authentication works, but I keep coming up dry. I know that much of this is probably trivial to a lot of you, which is why I am asking because it isn’t to me. Well, thanks in advance for any help that you can provide me.
I have an asp.net page which accesses a sql server database (on another server). I am trying to use impersonation to impersonate the domain user accessing the page and use the credentials to access the sql server using a windows login. I have windows authentication checked in IIS settings am using the following web.config:<configuration> <system.web> <authentication mode="Windows" /> <identity impersonate="true"/> <authorization> <allow users="*" /> </authorization> <customErrors mode="Off" /> </system.web> </configuration> I can connect fine when i open the page on the IIS server but from other machines, whilst logged in as the same domain user I get the error: Login error failed for user ''. Anybody know what the problem might be?
I have a query. I want to use sql server authentication for my asp.net application. I have created a seperate username and password for the sql server. Now I want to use that username and password to establish the connection thru web.config. In web.config, I don't want to give the username and password of sql server. Instead, I want to get those details in other ways. Please tell me how to handle the connection string with more security?
I have setup ODBC to connect to a SQL Server 200 database (evaluation version) so I can link tables into an Access database. In the ODBC setup, I selected SQL Server Authentication versus Windows Authentication. However, when I link a table into Access it still uses Windows Authentication first.
I found an article here that discusses the issue: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q279526
It suggested that I run an MDAC update to version 2.6. So I did that and I still have the same problem.
I tried to link a table through some code in Access by changing the connect string to "Trusted_Connection=No" but it still linked up with "Trusted_Connection=Yes".
If I set up my DSN using SQL Server Authentication am I then compelled to use a connection string to connect to the database (in order to supply the user name and password). At the moment every time my application tries to connect to SQL Server on a PC that has a DSN set up using SQL Server Authentication, a Login box pops up.
I'm writing some software for clients and the connection is done via de username passwd methode, not windows authentication. One of the salespeople is creating FUD now, talking about a "major security leak" because, if someone has the username / password, he can view the data in the mssql database. ( seems normal to me for a username/password combination - winNT or not - but this news can be shocking to the uninitiated) Is there any paper on his comprehensionlevel that deals with this issue? Or you've got an opinion on this?
recently i have intsalled sql server on my system . and tried to set the sql server authentication, but its giving me an error,all the time i.e not allowing me to register and it says, "not connected to the right server." or sql server is not found.
can any one help me out ASAP with this.that is show me how to register the sql server exactly and set the user name and password for the sql server.Thnaks.