Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build, protect and deploy apps across any platform and mobile device
Automate decision processes with a no-code business rules engine
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Over the past several months, I have been engaged in more security related connectivity projects than the previous several years combined. I’m still trying to figure out what’s driving this between data moving to clouds, corporate compliance, or government regulations across NIST, FISMA, STIGs, FIPS 140-2, etc.
Let’s break things down into an amazing security toolset you can use for SQL Server data connectivity, as well as other data sources.
I have been seeing this requirement a lot which is primarily driven by corporate compliance since Microsoft strongly discourages use of SQL Server authentication with a database and password. Therefore, databases supporting only NTLM Windows authentication become isolated from Unix/Linux environments where key business systems are running. You can learn more about our exclusive authentication from Unix/Linux to SQL Server via JDBC.
Yes, we do support NTLM Windows Authentication from Unix/Linux with ODBC as well.
Maybe your organization has selected Kerberos instead of NTLM authentication for cross platform support. However, what happens when you’re trying to authentication with SQL Server running in a different domain?
DataDirect has introduced support for Cross realm or domain Kerberos authentication by introducing a new property, ServicePrincipalName, to specify the target domain.
The value of this option is used along with the hostname and port specified to create the security context for kerberos:
"MSSQLSvc/" + serverName + ":" + portNumber + "@" + servicePrincipalName
I see this commonly when organizations acquire or integrate new business units into existing application infrastructure; or with organization wide data virtualization strategies using Composite Software, Denodo, or Informatica.
This requirement is driven by the movement of applications to the cloud, and sometimes sprinkled with a little compliance/regulation. DataDirect Cloud offers secure ODBC/JDBC connectivity over HTTPS to SQL Server databases that reside behind a firewall or cloud. Check out my previous article and Prezi on this topic, and I'm planning to host a related session at PRGS14 next month.
1. Download 15 day trial of the DataDirect Connect ODBC and JDBC SQL Server drivers to securely connect to your SQL Server databases. Or sign up for a trial on www.datadirectcloud.com for ODBC/JDBC over https.
2. Or call 1-800-876-3101 to learn more.
Sumit Sarkar is a Chief Data Evangelist at Progress, with over 10 years experience working in the data connectivity field. The world's leading consultant on open data standards connectivity with cloud data, Sumit's interests include performance tuning of the data access layer for which he has developed a patent pending technology for its analysis; business intelligence and data warehousing for SaaS platforms; and data connectivity for aPaaS environments, with a focus on standards such as ODBC, JDBC, ADO.NET and ODATA. He is an IBM Certified Consultant for IBM Cognos Business Intelligence and TDWI member. He has presented sessions on data connectivity at various conferences including Dreamforce, Oracle OpenWorld, Strata Hadoop, MongoDB World and SAP Analytics and Business Objects Conference, among many others.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.