Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
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
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
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
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
1. Windows Authentication
2. Mixed Authentication
Mixed Authentication is very much like the apples available in the Progress DataDirect kitchen in Morrisville, NC. Sometimes they’re good, and sometimes they’re risky. Microsoft strongly recommends the default mode, Windows Authentication, when possible. This is consistent with conversations I have had with DBAs and Application Teams that consider Mixed Authentication to be a security risk. Many of the conversations are with the Federal Government and Universities; and it's comforting to know they do not compromise when it comes to security. And this is when Progress DataDirect gets engaged since we have the best in class security features (both data encryption and authentication) across our full suite of data access solutions.
One of the reasons application teams are still using SQL Server Authentication is to support ODBC or JDBC drivers that do not support Windows Authentication. And these drivers are connecting critical applications such as Informatica, DataStage, SAS, DG4ODBC, IBM Cognos, Ab Initio, etc., running on AIX, Solaris, HP-UX, Linux servers. And if you are using SQL Server Authentication, it's quite possible your DBA is holding a major grudge against you and your application team. To get back on the DBA's good side, I recommend the following solutions to connect applications to SQL Server using Windows Authentication:
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 © 2018 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.