MSSQL JDBC Driver Single Sign On Auth from Unix 0.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News MSSQL JDBC Driver Single Sign On Auth from Unix 0.1 (Default branch)
# 1  
Old 01-12-2008
MSSQL JDBC Driver Single Sign On Auth from Unix 0.1 (Default branch)

libsqljdbc_auth provides support for using Windows integrated authentication with the Microsoft SQL Server 2005 JDBC Driver under Unix operating systems. SQL Server Authentication is not secure and is difficult to manage in an environment with large numbers of database servers, but it is often the only option when connecting to an SQL Server Database from non-Windows operating systems. This library allows users of other operating systems to use the more secure Integrated Authentication method with Microsoft's SQL Server 2005 JDBC driver using native Kerberos authentication libraries. License: BSD License (revised) Changes:
This is the initial release, enabling single-sign-on integrated authentication to SQL Server 2000 and 2005.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Linux expand dollar sign in single quotes

I am trying to get a dollar sign variable to be expanded in single quotes. Not sure what I am doing wrong. I have tried every way I can think of. for i in `cat file1` do for j in `cat file2` do ssh $i 'systemctl is-enabled "${j}" '; done done... (4 Replies)
Discussion started by: cokedude
4 Replies

2. Cybersecurity

differences between Shibboleth and Single Sign On

Could someone please explain to me the difference between Shibboleth and Single Sign On? How are they related? Thank you! (1 Reply)
Discussion started by: onlinelearner02
1 Replies

3. Hardware

Difference between platform driver,codec driver and Machine driver

In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

4. Solaris

Solaris Single Sign on options

We are looking for implementing solaris single sign on with AD in our environment which as few hundred Solaris hosts and couple of hundred solaris zones ..IS there any third party software for the same or we can do it by just making the solaris servers as AD clients ? Any help is appreciated. (1 Reply)
Discussion started by: fugitive
1 Replies

5. Shell Programming and Scripting

Perl script to connect to database using JDBC driver?

How to connect to SQL Server database from perl script using JDBC driver? ---------- Post updated at 05:33 PM ---------- Previous update was at 05:07 PM ---------- i have sqljdbc.jar file. by setting the class path how can i connect to the database using perl script? (2 Replies)
Discussion started by: laknar
2 Replies

6. Red Hat

Need a single printer driver added to CUPS

Just got an HP OfficeJet L7680 printer but there are no drivers for it in RHEL5. I just want to add the single driver without installing hplip 3.9.8. It's going to be connected with USB. Is this possible and if so how? (1 Reply)
Discussion started by: deloev
1 Replies

7. UNIX for Advanced & Expert Users

Problem: Single Sign On for linux

Hi gurus, I'd like to know your opions about Single Sign On (SSO) for linux (Debian). In my company, clients want to access to different services (FTP, HTTP, Mail, Web Applications ). I think about OpenLDAP and Proxy (Squid, Vulture) to resolve this problem but i'm not sure if they can. Are there... (0 Replies)
Discussion started by: thanhdat
0 Replies

8. Shell Programming and Scripting

Unix to Sql Server via JDBC

I am trying to connect SQL SERVER VIA JDCB. Following is something I tried and will appreciate any help what I am doing wrong Here's what I did, I tried several variations, but I keep getting this error: Exception in thread "main" java.sql.SQLException: Unable to connect. Invalid URL I... (1 Reply)
Discussion started by: cqldba
1 Replies
Login or Register to Ask a Question
DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server(3)User Contributed Perl DocumentatioDBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server(3)

NAME
DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server - Support specific to Microsoft SQL Server over ODBC DESCRIPTION
This class implements support specific to Microsoft SQL Server over ODBC. It is loaded automatically by DBIx::Class::Storage::DBI::ODBC when it detects a MSSQL back-end. Most of the functionality is provided from the superclass DBIx::Class::Storage::DBI::MSSQL. USAGE NOTES
Basic Linux Setup (Debian) sudo aptitude install tdsodbc libdbd-odbc-perl unixodbc In case it is not already there put the following (adjust for non-64bit arch) in "/etc/odbcinst.ini": [FreeTDS] Description = FreeTDS Driver = /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so Setup = /usr/lib/x86_64-linux-gnu/odbc/libtdsS.so UsageCount = 1 Set your $dsn in connect_info as follows: dbi:ODBC:server=<my.host.name>;port=1433;driver=FreeTDS;tds_version=8.0 If you use the EasySoft driver (<http://www.easysoft.com>): dbi:ODBC:server=<my.host.name>;port=1433;driver=Easysoft ODBC-SQL Server Basic Windows Setup Use the following $dsn for the Microsoft ODBC driver: dbi:ODBC:driver={SQL Server};server=SERVERSQL_SERVER_INSTANCE_NAME And for the Native Client: dbi:ODBC:driver={SQL Server Native Client 10.0};server=SERVERSQL_SERVER_INSTANCE_NAME Go into Control Panel -> System and Security -> Administrative Tools -> Data Sources (ODBC) to check driver names and to set up data sources. Use System DSNs, not User DSNs if you want to use DSNs. If you set up a DSN, use the following $dsn for connect_info: dbi:ODBC:dsn=MY_DSN MULTIPLE ACTIVE STATEMENTS
The following options are alternative ways to enable concurrent executing statement support. Each has its own advantages and drawbacks and works on different platforms. Read each section carefully. For more details about using MAS in MSSQL over DBD::ODBC see this excellent document provided by EasySoft: <http://www.easysoft.com/developer/languages/perl/multiple-active-statements.html>. In order of preference, they are: o mars o dynamic_cursors o server_cursors METHODS
connect_call_use_mars Use as: on_connect_call => 'use_mars' in your connection info, or alternatively specify it directly: Your::Schema->connect ( $original_dsn . '; MARS_Connection=Yes', $user, $pass, \%attrs, ) Use to enable a feature of SQL Server 2005 and later, "Multiple Active Result Sets". See "Does DBD::ODBC support Multiple Active Statements?" in DBD::ODBC::FAQ for more information. This does not work on FreeTDS drivers at the time of this writing, and only works with the Native Client, later versions of the Windows MS ODBC driver, and the Easysoft driver. connect_call_use_dynamic_cursors Use as: on_connect_call => 'use_dynamic_cursors' Which will add "odbc_cursortype => 2" to your DBI connection attributes, or alternatively specify the necessary flag directly: Your::Schema->connect (@dsn, { ... odbc_cursortype => 2 }) See "odbc_cursortype" in DBD::ODBC for more information. If you're using FreeTDS, "tds_version" must be set to at least 8.0. This will not work with CODE ref connect_info's. WARNING: on FreeTDS (and maybe some other drivers) this will break "SCOPE_IDENTITY()", and "SELECT @@IDENTITY" will be used instead, which on SQL Server 2005 and later will return erroneous results on tables which have an on insert trigger that inserts into another table with an "IDENTITY" column. WARNING: on FreeTDS, changes made in one statement (e.g. an insert) may not be visible from a following statement (e.g. a select.) WARNING: FreeTDS versions > 0.82 seem to have completely broken the ODBC protocol. DBIC will not allow dynamic cursor support with such versions to protect your data. Please hassle the authors of FreeTDS to act on the bugs that make their driver not overly usable with DBD::ODBC. connect_call_use_server_cursors Use as: on_connect_call => 'use_server_cursors' May allow multiple active select statements. See "odbc_SQL_ROWSET_SIZE" in DBD::ODBC for more information. Takes an optional parameter for the value to set the attribute to, default is 2. WARNING: this does not work on all versions of SQL Server, and may lock up your database! At the time of writing, this option only works on Microsoft's Windows drivers, later versions of the ODBC driver and the Native Client driver. AUTHOR
See "AUTHOR" in DBIx::Class and "CONTRIBUTORS" in DBIx::Class. LICENSE
You may distribute this code under the same terms as Perl itself. perl v5.18.2 2013-12-16 DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server(3)