Hi Sanjay;

  The only way today to have TLS 1.2 connectivity to SS (AFAIK) would be to use the ODBC type of DB connection option.

FYI:  https://blogs.msdn.microsoft.com/sqlreleaseservices/tls-1-2-support-for-sql-server-2008-2008-r2-2012-and-2014/

BTW: PB "DB Client" support for TLS 1.2 support within PB Apps is being scheduled for support in PB2019R3.

Regards ... Chris

Chris,

Microsoft bought back SQLOLEDB provider under new name MSOLEDBSQL driver. Do you think that also an option?

https://www.microsoft.com/en-us/download/details.aspx?id=56730

Thanks!

   The only other protocol that might work today is ADO.net - within the "Provider" middle-ware - as ADO.Net does support TLS 1.2 currently in newer .Net framework versions.

As per this blog;

https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/

".NET 4.6 and above. You don’t need to do any additional work to support TLS 1.2, it’s supported by default."

I feel .NET 4.6 or higher isn't a problem it's just PowerBuilder and Providers. Thanks!

As PB 2019 R3 supports TLS 1.2, could you let us how exactly do we certify our code?

Are there any changes required on SQL Server? We are using MS OLE DB SQL Driver which PB 2019 R3 supports.

Are there any changes required on Client desktops?

Do they both have to be on TLS 1.2 only etc..

Do you have some kind of a white paper which describes steps to prove our upgraded code definitely works with TLS 1.2?

These might be silly questions but if you could guide us in a proper direction our certification process will become smoother.

Thanks

Sanjay

Hi Sanjay;

  FYI: TLS 1.2 support for SQL Server was just added to the recently released PB2019R3 product.

http://docs.appeon.com/pb2019r3/whats_new/MS_SQL_Server_enhancements.html

  From the SS side ...

http://support.microsoft.com/en-us/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe

Regards ... Chris