Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (6)

Resolved PowerBuilder and TLS 1.2 Support

  1. How-to
0
Votes
Undo
  1. Sanjay Shivade
    Sanjay Shivade
  2. SnapObjects
  3. Friday, 6 December 2019 17:02 PM UTC

Hi,

The following dbparm configuration required for TLS 1.2 pb connection object is erroring out with the attached error.

SQLCA.DBParm = "Database='EnvisionFunds',TrimSpaces=1,TrustedConnection=1"

It's looking for domain user even though domain user has nothing to do with this.

I was told previously that it's required for TLS 1.2. Is that changed in PB 2019 R3 Build # 2728?

Am I missing something? 

Thanks

Sanjay

 

 

 

Attachments (1)
tls 1.2 error.JPG tls 1.2 error.JPG
  1. TLS/SSL
SqlExecutor.Select Question
.NET Datastore retrieve and subsequent SqlExecutor...
Responses (6)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 11 March 2021 19:38 PM UTC
  2. SnapObjects
  3. # 1

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

Comment
There are no comments made yet.
Sanjay Shivade
Sanjay Shivade Accepted Answer Pending Moderation
  1. Thursday, 11 March 2021 17:49 PM UTC
  2. SnapObjects
  3. # 2

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

 

Comment
Load more comments
Roland Smith
  1. Roland Smith
  2. Thursday, 11 March 2021 18:37 PM UTC
All I see in the DBParm help is TrustedConnection=1. The only references to TLS have to do with HttpClient.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Thursday, 11 March 2021 18:39 PM UTC
There is also Encrypt=1 but nothing to specify TLS level.
  1. Helpful
Sanjay Shivade
  1. Sanjay Shivade
  2. Thursday, 11 March 2021 18:42 PM UTC
Thanks, we will give it a try.
  1. Helpful
There are no comments made yet.
Sanjay Shivade
Sanjay Shivade Accepted Answer Pending Moderation
  1. Friday, 6 December 2019 21:10 PM UTC
  2. SnapObjects
  3. # 3

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!

 

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 6 December 2019 22:39 PM UTC
Are you talking about supporting TLS 1.2 for the PowerScript targets or the C# targets of PowerBuilder 2019?
  1. Helpful
Sanjay Shivade
  1. Sanjay Shivade
  2. Monday, 9 December 2019 17:39 PM UTC
PowerScript targets
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 9 December 2019 17:58 PM UTC
PowerScript is not a .NET language so it doesn't natively interface with ADO.NET. If you have a chance, please try the new C# targets in PowerBuilder 2019 and let us know if that has any problems.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 December 2019 20:45 PM UTC
  2. SnapObjects
  3. # 4

   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.

Comment
There are no comments made yet.
Sanjay Shivade
Sanjay Shivade Accepted Answer Pending Moderation
  1. Friday, 6 December 2019 20:18 PM UTC
  2. SnapObjects
  3. # 5

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!

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 6 December 2019 20:40 PM UTC
We are working on supporting this, especially since Microsoft has discontinued the native client for SQL Server.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 December 2019 19:50 PM UTC
  2. SnapObjects
  3. # 6

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

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.