Re: Changing passwords / Blocking SA login attempts

From: Fox (fox@connexions.net)
Date: 02/13/03 

From: "Fox" <fox@connexions.net>
Date: Thu, 13 Feb 2003 14:24:36 -0500

OK, now I understand all the ramifications. I guess I can look into the
templates
and figure out how to change them. But I now have a more urgent issue.

I did as you suggested, but now have a serious problem. Since I changed to
Windows Authentication, I can no longer access Enterprise Manager.

I am guessing that the Start SQL server account I had in there was not
a Trusted Account. I had my name in there probably as an SQL
authentication. Now that I screwed myself, what must I do to get
back into Enterprise Manager ;)

Regards,
Fox

"BP Margolin" <bpmargo@attglobal.net> wrote in message
news:eiLlz1w0CHA.2296@TK2MSFTNGP10...
> Fox,
>
> The authentication mode covers **all** connections to SQL Server. The
> purpose of Windows Authentication is not just to "thwart" the sa account
...
> that is simply a "side-effect" of changing to Windows Authentication.
>
> Windows Authentication is more secure because, for example, SQL Server has
> no mechanism to require that users periodically change passwords, or to
> enforce password standards. Windows does have those abilities.
>
> Basically the idea behind Windows Authentication is that SQL Server relies
> upon the Windows operating system to authenticate that a user is who he
says
> he is. After that, the SQL Server administrator can choose which Windows
> users or Windows groups to access the SQL Server databases. But the basic
> authentication process is left to Windows rather than to SQL Server.
>
> -------------------------------------------
> BP Margolin
> Please reply only to the newsgroups.
> When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
> can be cut and pasted into Query Analyzer is appreciated.
>
> "Fox Bortniker" <fox@connexions.net> wrote in message
> news:OmCMaEw0CHA.2076@TK2MSFTNGP10...
> >
> >
> > Great, that brought me to it. Just one question. I have a pre-existing
> > set of templates running in a database that are in PHP. They are
> > numerous and complex. They use my name for login via SQL. If I change
> > the authentication to Windows where you said to do so, is that for all
> > authentication or is that just for the SA account ? I am afraid that if
> > I change that, the other template will not allow me to log in as the
> > admin for the application. Is this going to happen ? Will I need to find
> > out how to change the log in that is built into that set of templates so
> > I can change it as well ?
> >
> > Thanks,
> > Fox
> >
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it!
>
>

Relevant Pages

  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Remote connection failed
    ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
    (microsoft.public.sqlserver.connect)
  • Re: Changing passwords / Blocking SA login attempts
    ... I went into the Server Config properties and changed to Windows ... My login for Start and Run SQL server was in this format. ... I am supposing this was an SQL authentication, ...
    (microsoft.public.sqlserver.security)
  • Windows Authentication with IIS on separate machines
    ... Yes, setting Basic Authentication in IIS works, but the ... >in SQL server but doesn't work if user account was ... >imported from a Windows account. ...
    (microsoft.public.sqlserver.security)
  • Re: server authentication & ASP authentication
    ... on to the client workstation with an authorized Windows account. ... SQL Server with Windows authentication. ...
    (microsoft.public.sqlserver.security)