Authentication permissions

Similar Threads:

1.ADMTv3 and SQL Windows authentication permissions

I'm planning on moving a SQL Server 2000 2-node cluster in a Windows 2000 
domain that uses Windows authentication to a Windows 2003 domain. Can the 
ADMTv3 modify the SQL permissions or is there another tool available that can 
handle that function?

2.Authentication/Permissions Configuration for RS/IIS?

I am making raw (not using the .NET framework) SOAP calls to RS web services 
from Classic ASP but have run into multiple RS permission and IIS logon 
failure problems.

I first created a new user on the machine (RSUser) and have given 
permissions for the user as a System User, and Browser and Publish on the 
Home directory (which includes my reports) with SSMS.

I also gave Full Control to RSUser for the directory holding the reports.

When I configure the ReportService website via IIS for Anonymous access 
(using Machine\RSUser) and then make a call to ListSecureMethods method I 
get an XML SOAP response with the ServerInfoHeader as expected. But when I 
try to call the LoadReport method, I get a "The permissions granted to user 
'Machine\RSUser' are insufficient for performing this operation" (in the XML 
SOAP response).

What am I missing with respect to permissions/logons to let my ASP pages 
make calls to web service methods of RS?

How should IIS actually be configured to work with RS via the public 
Internet (i.e. not requiring end-users to supply passwords and such)?

Thanks for any help or examples. 

3.General authentication problem windows authentication as SQL authentication

Hello,

I have a problem with environment of two Windows Server 2008
Enterprise x64  systems:
1. AD
Domain Controller
SQL Server 2008

2. CRM
Microsoft Dynamics CRM 4.0
IIS

1. CRM works fine.
2. I can connect to SQL server from CRM using SQL Server Management
Studio as "sa" and as domain user. I can see databases > tables, but
when I try to open table I get unhandled exception.

3.  On CRM I have some web sites  which collects data directly from MS
CRM database using integrated security (from filtered views). Web site
is in the same Application pool as MS CRM. When I am logged in to the
CRM as domain administrator and open this site (web site is in "local
intranet" with automatic logon with current username and password
enabled) the sites connects to DB and collects data with no problems.

4. But when I am logged in to CRM as user other than DOMAIN
\administrator but also with domain administrator rights (also CRM
user with System Administrator role) the site tries to connect to SQL
as NT AUTHORITY\ANONYMOUS LOGON.

5. When I log in as DOMAIN\administrator to AD and open the same site
(web site is in "local intranet" with automatic logon with current
username and password enabled) the site tries to connect to SQL as NT
AUTHORITY\ANONYMOUS LOGON.

I remind that the site use Integrated security in connection string
and works OK the this user logged in to CRM.


Some history...
AD was domain controller (domain: domain1) and CRM was connected to
this domain.
AD was reinstalled and set as domain controlled (domain: domain2) and
CRM was connected to new domain.


Right now we have totally no idea what can be a problem :/

Any suggestions?

4.Using Widows Authentication and accesssing SQL with SQL Authentication

Hi

I am working on an application with .NET 2005 and SQL server 2000.

I am using windows authentication for my web application authentication
and trying to connect to the SQL server with SQL authentication
credentials.

My web.config reads as follows:

web application Authentication:

 <authentication mode="Windows" />
    <authorization>
      <allow users="*" />
      <!-- Allow all users -->
      <!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
    </authorization>
    <identity impersonate="true" />

SQL Authentication:

<connectionStrings>
    <add name="DevDBConnection"
connectionString="Server=MyServer;database=MyDB;uid=MyUser;pwd=MyPwd;"
      providerName="System.Data.SqlClient" />
     </connectionStrings>

MY IIS directory security is set to "Integrated Windows
authentication". I am validating the user againt the Active Directory
for authentication and reading the user details and groups which works
fine.

But trying to open a connection object fails. I am getting a
"{"Cannot open database requested in login 'MyDB'. Login
fails.\r\nLogin failed for user 'MyUser'."}"

I have tried searching for a solution to my best, but could not solve
this problem.

I hope some one might have come accross the same problem ahd looking
forward for your help.

Thanks,
Valar

5.connect to SQL server: windows authentication / SQL Server authentication

I have install a while ago a SQL server on my home computer.
now, due to my work, I'm more confident with it and want to play around with
it at home.
I try to make a connection string to it and I keep having error:
---------------------------
SQL Query Analyzer
---------------------------
Unable to connect to server HERMES:

Server: Msg 18452, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'lloyd'. Reason: Not associated with a trusted SQL Server connection.
---------------------------
OK
---------------------------


I try play around with user role, etc ... in SQL Enterprise manager, no way
I manage user lloyd to work.
this drives me crazy, how could I connect to this database.

(apparently windows authentication work, but I DON'T want to use it, I want
to use a login/password !)

BTW I was wondering, I don't really understand how windows authentication
work, nowhere I manage to find the right granted to myself or user ASP_NET,
where could I find that ?

6. SQL sever 2005 express move windowns authentication choice to mixed authentication

7. Change from SQL Authentication -> Windows Authentication failed

8. Slow Windows Authentication vs Fast SQL Authentication