1. Amit De Picciotto
  2. PowerBuilder
  3. Monday, 31 January 2022 14:34 PM UTC


Beginning today, DEV azure stopped to support TLS 1.0 & 1.1 https://devblogs.microsoft.com/devops/deprecating-weak-cryptographic-standards-tls-1-0-and-tls-1-1-in-azure-devops/#:~:text=Per%20Microsoft's%20position%20to%20protect,minimum%20from%20January%2031%2C%202022.

Unfortunately, it seems that MSSCCI use the TLS 1.0 protocol

MSSCCI is the tool that allow us to connect the Power Builder application to the source control (TFS), so now it broke and developers cannot check out and check in their code.


One alternative to is upgrade to GIT (from 2017 R3) but it pricy, very pricy for product that is on production.


Is there any other alternative, beside GIT?


Amit De Picciotto Accepted Answer Pending Moderation
  1. Monday, 31 January 2022 15:31 PM UTC
  2. PowerBuilder
  3. # 1


Agree, GIT it where the source of PB should be

In the meantime, work on workaround with this: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-tls-enforcement#enable-tls-12


Indeed this registry entries seems to do the job

I will be happy to update if anything will pop-up



There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 31 January 2022 15:22 PM UTC
  2. PowerBuilder
  3. # 2

You should use Git or SVN… those are the two options natively supported in PB and not using obsolete MSSCCI.  
Git and SVN are open source so lots of implementations and price all over the place including free.

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.