Windows Authentication on SP 14 Server

Hi,
i want to achieve Windows Authentication on SP 14 Server.
which is the best way?
Thanks in advance
Regards,
Bobu

You can go for Kerberos Authentication. There are plenty of weblogs and forum discussions on this.
Windows Integrated Authentication via Kerberos on an LDAP data source
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b69f6f89-0a01-0010-1198-ba7fff95a2ec
Regards,
Piyush
ps: please award points if useful.

Similar Messages

"Windows Authentication Mode" when SQL Server 200 and CF on different machines?

Hi All,
I am playing for two days with following problem. And still I
did not able to get rid of it.
I have installed SQL Server 2000 on machine which is my
server (windows 2003 server) and this machine is my domain
controller. I have user “ABC” user and I have added
this user in administrator group.
I have another machine where OS is Windows XP and CF 7 is
installed. I create an ODBC Connection from Administrative Tool to
my Database (windows 2003 server) successfully.
Now when I create Data Socket in Coldfusion Administrator and
when I select the my ODBC that I had created and when I Submit it
then CF admin throughs the following message.
Connection verification failed for data source: myTest
java.sql.SQLException: [Macromedia][SequeLink JDBC
Driver][ODBC Socket][Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Please Brother, I don’t have any Clue to solve it,
Please help.
One Important thing, All this working fine if my CF, and SQL
Server are on same machine.
Best regards,
Shahid

Hi Phil Thanks,
Finally i able to configure it out..... following are the
steps...
I assume domain controller is properly configure.
Following are the steps for the machine where SQL SERVER 2000
is installed
1- We need to create Login account for your domain account in
SQL Server 2000 using Enterprise Manager.
• Right Click -> New Login
• Click to load the domain users, select any user from
your domain that will connect to your SQL Server from LAN.
Following are the steps for the machine where ColdFusion and
IIS are installed.
Step No. 1
Stop ColdFusion MX.
Backup your existing macromedia_drivers.jar file.
Unzip macromedia_drivers.zip into the same directory,
overwriting the previous
macromedia_drivers.jar.
You can download “macromedia_drivers.zip” from
following URL
http://kb.adobe.com/support/coldfusion/ts/documents/1a3c2ad0/macromedia_drivers.zip
A new file, DDJDBCAuth03.dll, which is required for Windows
Authentication, is also included in the zip file replacing the
older DDJDBCAuth.DLL.
Restart ColdFusion MX.
ColdFusion MX loads the JDBC drivers inmacromedia_drivers.jar
in the directory cf_root/lib. For example, with ColdFusion MX 7
Server Configuration on Windows installed on drive C:, this would
beC:\CFusionMX7\lib\macromedia_drivers.jar.
Then restart Machine
Step No. 2
Configure all the ColdFusion Services to “Log On
As” using the Domain User Account configured in SQL Server in
the above mentioned step.
Change the “Log On As” similar for the all other
Cold fusion services (ColdFusion MX 7 ODBC Agent, ColdFusion MX 7
ODBC Server, ColdFusion MX 7 Search Server).
Step No. 3
Restart the services; for the safe side reboot the system.
Step No. 4
Create ODBC (Control Panel -> Administrative Tool ->
Data Sources (ODBC)) using the windows NT Authentication option to
connect to database.
Step No. 5
Create Data Socket and Select the created ODBC connection in
the Drop down (ColdFusion-> Admin)
Thanks to all who participated in this discussion...
With lots of Thanks to All particular to Phil who guided me
in right direction,
Shahid

Windows Authentication using Microsoft SQL Server 2005 JDBC Driver

Hi,
I am using Microsoft SQL Server 2005 JDBC Driver to connect to SQL Server 2000 database, can anyone tell me the connection URL for windows authentication. SQL authentication is working fine.
DataDirect has drivers for windows authentication but I am not using it.
Regards
Arup

You can't do it with the Microsoft driver. There's a free driver called jTDS that may be able to (I don't know).
(edit) Looking at their FAQ it looks like it does:
http://jtds.sourceforge.net/faq.html

HOW TO CREATE WINDOWS AUTHENTICATION USER IN SQL SERVER AFTER INSTALLING SQL SERVER 2008

I had an error while executing asp.net appcation from IIS as follows
Login failed for user 'IIS APPPOOL\ASP.NET v4.0'.
Description:
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'IIS APPPOOL\ASP.NET v4.0'.
[SqlException (0x80131904): Login failed for user 'IIS APPPOOL\ASP.NET v4.0'.]
Can the above problem be solved by CREATING WINDOWS AUTHENTICATION LOGIN FOR
'IIS APPPOOL\ASP.NET v4.0' ?
If yes, how to create the login?
If no,what is the best possible solution?
Please reply as soon as possible as i am unable to run my project which I had done in my lab,in my home system.

Hi Praveen,
To fix this issue, you need to change the Identity of your website's Application Pool to use the
NetworkService account (or the less secure LocalSystem account). By default, IIS7 seems to set the Application Pools Identity to 'ApplicationPoolIdentity' instead of NetworkService or LocalSystem.
Here's a step-by-step guide for determining your websites Application Pool, then changing its Process Model Idenitty in IIS7:
1.Open Internet Information Services (IIS) Manger.
2.In the Connections sidebar, drill down into Default Web Site and click on your website.
3.Now in the Actions sidebar (on right side), click on Advance Settings... In the popup box, under General you will see your Application Pool listed for your website (in my case the app pool is: ASP.NET V4.0).
4.Click Cancel... If you choose, you can change the Application Pool here, but for the sake of this example we just wanted to find out what the website's App Pool was.
Then change the app pool's (Process Model) Identity to 'NetworkService', the steps are showed as below:
1.Open Internet Information Services (IIS) Manger.
2.In the Connections sidebar, click on Application Pools.
3.Now right-click on theApplication Pool that your website is using (in this case my site is using the ASP.NET v4.0 application pool), and select Advanced Settings... from the menu.
4.In the Advanced Settings pop-up box, locate the Process Model -> Identity section and click on the Application Pool Identity.
5.In the Application Pool Identity pop-up box, change the Built-in account to NetworkService (or if you want LocalSystem), then click OK, and click OK again to save your Advanced Settings changes.
Hope this helps.
Best Regards,
Peja
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Users using Windows Authentication unable to login after upgrade to SQL Server 2012 SP2 CU1

We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 CU1. Upgrade was successful. Users that have SQL Server Management Studio 2012 can successfully log in via Windows Authentication, but users with an older version of SQL Server Management
Studio are unable to log in via Windows Authentication.
The error they receive is listed below:
Connect not connect to XXXXXXX
Login Failed. The login is from an untrusted domain and cannot be used with Windows Authentication.
(Microsoft SQL Server, Error: 18452)
If we switch to Mixed authentication, users can log in via SQL Server Authentication.
Our security policy prohibits SQL Authentication.
Outside of having the staff upgrade to SQL Server 2012 SQL Server Management Studio, is there any setting I can set/unset to allow older version of SQL Server Management studio to connect to SQL Server 2012?
Thanks.
DJ

Glad to see that you were able to resolve the issue yourself, but for the curious, could you explain what this
Extended Protection is?
Erland Sommarskog, SQL Server MVP, [email protected]

Windows Authentication and Zenworks Problem

I have Zenworks 6.5.1.0 on my desktop. I make my computer part of our
win2k3 domain. When I try to connect to sql server through the client
tools using windows authentication the domain name doesn't show up
correctly. It will show up as the computer_name/username instead of
domain/username. This is also a problem for trying to setup applications to
use windows authentication instead of sql server authentication.
If I uninstall zenworks the problem goes away. Nevertheless, this isn't a
solution. I would appreciate any info you can give.

OK, here is what I would do pending more input from you..........
1)Setup IDM (Identity Mgr) to synch all E-Dir IDs into the Domain.
You should have this product for free if you have Maint on ZEN or NetWare)
2)On all PCs in the Domain, push this key to block the use of DLU.
Now every user will be able to use any PC.
If the PC is in the Domain, they will use domain authentication.
If the PC is not in the Domain, they will use DLU to logging automatically.
craig wilson wrote:
> There is not reason they can't authenticate afterwards to the domain.
> The user's would just need provide their ID/Pwd.
>
> Do all of your NDS Users have AD Accounts?
> Are the Passwords Synched?
> How big is this network? How far along is the Domain deployment?
>
>
> [email protected] wrote:
>> Is there an option to setup the users to have dynamic local user so they
>> can login to any workstation, but also be able to use windows
>> authentication? I think the solution might work below since right now
>> I am
>> only wanting to do this for one workstation in particular, but it would
>> really be great to be able to use windows authentication through out all
>> custom built apps.
>>> Somebody has defined a "DynamicLocalUser" policy with Zenworks.
>>> This causes any attempt to logon to the domain to be over-ridden an a
>>> local account is created and used on your PC.
>>>
>>> In general these "DLU" policies are used in non-domain environments.
>>>
>>> If you want to disabled "DLU" on your workstation.....
>>> See http://support.novell.com/docs/Tids/.../10071463.html
>>>
>>>
>>>
>>> [email protected] wrote:
>>>> I have Zenworks 6.5.1.0 on my desktop. I make my computer part of our
>>>> win2k3 domain. When I try to connect to sql server through the client
>>>> tools using windows authentication the domain name doesn't show up
>>>> correctly. It will show up as the computer_name/username instead of
>>>> domain/username. This is also a problem for trying to setup
>>>> applications to
>>>> use windows authentication instead of sql server authentication.
>>>> If I uninstall zenworks the problem goes away. Nevertheless, this
>>>> isn't a
>>>> solution. I would appreciate any info you can give.
>>>
>>> --
>>> Craig Wilson
>>> Novell Product Support Forum Sysop
>>> Master CNE, MCSE 2003, CCN
>>
>
>
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN

How to resolve a windows authenticated orphaned user in Sql Server 2008 R2?

Hi,
We have some orphaned windows authenticated users(domain) in the database while it had been
migrated from Sql Server 2005 to Sql Server 2008 R2, because there are no corresponding
logins for the users. Will just adding the logins would be sufficient or after adding the
logins should we also run sp_change_users_login @Action='update_one' to resolve any sid
conflict. Thanking you in advance,
With regards
Binny Mathew

Binny
You have issue with orphaned users if you use Mixed Authentication. If you use Windows and move the db to the new server the Windows Login should be exist on the new server already.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

Hi there,
I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
instances.
A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
Currently both instances are running on same node.
While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
Please help resolve the issue.
Thanks,
AY

Hello,
I Confirm that I encountred the same problem when the first domain controller was dow !!
During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
When the firts DC restart finishied restarting every thing was Ok !
The Question here : Why the cluster instance does'nt used the second DC ???
Best Regards
J.K

Data Modeler 2.0.0 Windows Authentication to SQL Server

Is there a way to sign onto a SQL Server database with Data Modeler similar to SQL Developer using Windows Authentication? I have loaded the correct JDBC drivers.

It wasn't possible for me (Win XP) but you can try using following steps:
1) get JDBC driver from Microsoft site - http://msdn.microsoft.com/en-gb/data/aa937724.aspx - you can use 1.2 or 2.0
2) copy sqljdbc_auth.dll to windows\system32 directory as described here http://msdn.microsoft.com/en-us/library/ms378428.aspx
3) add JDBC driver as third party driver in General options (Data Modeler)
4) add ;integratedSecurity=true to port information (or database) - my port looks "1779;integratedSecurity=true"
It doesn't work due strange incompatibility between the way we use connections and JDBC driver implementation related to usage of sqljdbc_auth.dll - may be it will work for you :). We have it fixed and fix will be included in next patch release.
Philip

JDBC driver for SQL Server 2000 with windows authentication

Does anyone know of a JDBC driver for SQL Server 2000 that supports Windows Authentication, that is that a username and password does not need to be supplied when connecting to the database.

You can use the JDBC-ODBC-Bridge.
ODBC provides windows-authentication.
Hope it helps.
Freddy

SQL Server Window Authentication Slow

Hi
We are using SQL Server 2012. When we run our applications with window authentication it runs really slow. But if we use same application with database user authentication then it runs really fast.
Any Suggestion?
thanks
Drew

Hi Drew,
When you use Windows Authentication I assume your are using domain accounts (no local account). Your database server has probably some issue connecting to Active Directory. You might have similar delay logging on to the server using a domain account and
or rebooting the server might also be slow. Most likely your DNS server settings on that server or on your client are incorrect or out of date.
You can check this from the Command Prompt with the IPCONFIG.EXE /ALL command. Make a note of configured DNS servers. The configured DNS servers should ONLY be the DNS servers from the Active Directory domain (typically those are the same servers as the
domain controllers). You should remove any DNS servers from the Internet.
Why does this matter? You may ask. SQL Server needs to connect to the domain controller to verify your credentials. to that it first needs to know the IP address of the domain controller. This information is stored on a DNS server in your Active Directory
domain, not on public DNS servers on the Internet. If your server is configured with public DNS servers from the Internet, requesting this information will fail and cause an delay until either a correct DNS server is contacted or the domain controller is contacted
using legacy (NTLM) methods.
You may have a more complicated situation if more Active Directory domains are involved (e.g. domain trusts, forest trusts, complex nested group memberships.), or if the configured Domain Controller is located at another site and is only connected by a slow
link, or there is actually a performance issue with your domain controllers. In that case your Active Directory Administrator may supply with more information.
In short: check your DNS server settings.
Hope this helps.

SQL Server 2012 (Server Authentication), Is it possible to add Server Authentication after a Windows Authentication installation

I installed SQL Server 2012 to use Windows Authentication. An the tool I'm using to replicated data to the SQL Server 2012 database wants to use the (Server Authentication) mode. Is it possible to add a Server Authentication useID and Password?
Please let me know your thoughts.

Hi
You can change SQL Server Authentication by right clicking on the server instance and @Server Properties, Choose SQL Server and Windows Authentication Mode as shown in the image below
You have to restart the SQL Server for this to come into effect.
After this you are good to go for creating SQL Logins and using them.
Hope this helps.
Thanks,
BHanu

JDBC Connectivity for SQL Server 2005 Windows Authentication Mode

Hi Everyone,
In my Scenario we are using SQL Server 2005 with Mixed Mode Authentication. Now we are planning to move only with Windows Authentication Mode.
We have configured DB with Window authentication mode & user id have been configured in PI channels however we are getting error. We checked microsoft site, which says Windows Authentication mode DB can not be connected using JDBC drivers.
http://support.microsoft.com/kb/313100
In this above link see Basic Connectivity Troubleshooting Section.
Please let me know if someone confirued JDBC Channel Successfuly with Windows Authentication Mode.
Thanks In Advance
Regards,
Bharathi.

I think this issue is related to the way that Vista, Windows 7 and Windows 2008 / 2008 R2 treat users who are logged on to the system with an account that is a member of the local administrators group when SQL is running locally.
If your SQL setup has left you with BUILTIN\Administrators being a member of the sysadmin server role and you start up SQL Management Studio you'd expect to be mapped to the sysadmin role if your user account is in the local administrators group, however
these OS disable this ability and when you try to connect to the database engine SQL server doesn't know you are a member of the local administrators group.
To get round this, close all your open SQL management studio windows and then start a new window by right clicking the icon in the start menu and chosing to run as administrator. This time when you try to connect to the SQL database engine, windows doesn't
"hide" the fact that you are an administrator. If you need to do this a lot you can go to the compatibility tab on the properties of the shortcut and set it to always run as administrator.
Alternatively you can install the admin tools remotely and you don't get this effect.
Tim

SQL Server connections using SSPI (Windows Authentication)

v1.1 now has the ability to connect to third party databases. I have found a small bug with connecting to SQL Server though. Here are the steps to reproduce -
1. Download the jTDS JDBC Driver driver
2. Extract jtds-1.2.jar from the zip file to sqldeveloper\jdbc\
3. Extract Sso\ntlmauth.dll from the zip file to C:\Windows\System32\
4. In SQL Developer, go to Tools > Preferences > Database > Third Party JDBC Drivers, and click Add Entry...
5. Select sqldeveloper\jdbc\jtds-1.2.jar
6. Click OK
7. Right click on the Connections node and select New Connection...
8. Set the following values -
* Connection Name: SERVER_NAME
* Username: LEAVE BLANK (to use Windows Authentication)
* Password: LEAVE BLANK (to use Windows Authentication)
* Save Password: TICKED
* SQLServer > Hostname: SERVER_NAME
9. Click Test. You get a "Success" message.
10. However when you click Connect, it refuses to let you continue without providing a Username/Password. It should allow blank username/password because I have explicitly ticked "Save Password", and a blank username/password combination indicates that I wish to use SSPI (Windows Authentication)

Windows authentication is not supported in this release.

SQL Server 2008 Windows Authentication

Hi Team,
I am using SQL Instance and Window Authentication in this case it is taking user name as my local domain\username.
But the instace is of different domain which I want to access and want to change that domain name and user name.
Can I change it If yes how I can able to change it..Pl help me .
Yogesh Rawat

Hi Yogesh,
According to your description, you are going to connet to a SQL Server instance that in another domain using Windows authentication, right?
Generally, there are two approaches commonly used to get around this problem, adding your machine to the remote domain, or making your local domain trusted. For the details, please refer to the link below.
http://www.mssqltips.com/sqlservertip/3250/connect-to-sql-servers-in-another-domain-using-windows-authentication/
Regards,
Charlie Liao
TechNet Community Support

Windows Authentication on SP 14 Server

Similar Messages

Maybe you are looking for