Planning Analytics

Hello, great day!

I'm trying to make new Git requests within the TM1 REST and I'm receiving an error warning me of the depreciation of my SSH. However, this deprecation is not true, as my ssh was updated to the latest possible, as indicated by Microsoft itself (https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/comment-page-2/#comments). Anyone suffering from the same problem? Any solution? Or can we accept that this is just an update bug?

Thanks!

Error message:
"TM1 Git failed to connect to remote. Reason: remote: Command git-upload-pack: You're using ssh-rsa that is about to be deprecated and your request has been blocked intentionally. Any SSH session using SSH-RSA is subject to brown out (failure during random time periods). Please use rsa-sha2-256 or rsa-sha2-512 instead. For more details see https://aka.ms/ado-ssh-rsa-deprecation. remote: ERROR_SSH_UNSUPPORTED_CIPHER (7)."

------------------------------
João Caparroz
------------------------------

Hi João,

We're aware of that problem (especially with Git Azure) and producing the fixes quickly.

The PA on-premises v 11 is going to receive the fix shortly this month, following with fixes for v12.

Best regards,

Hello, great day!

I'm trying to make new Git requests within the TM1 REST and I'm receiving an error warning me of the depreciation of my SSH. However, this deprecation is not true, as my ssh was updated to the latest possible, as indicated by Microsoft itself (https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/comment-page-2/#comments). Anyone suffering from the same problem? Any solution? Or can we accept that this is just an update bug?

Thanks!

Error message:
"TM1 Git failed to connect to remote. Reason: remote: Command git-upload-pack: You're using ssh-rsa that is about to be deprecated and your request has been blocked intentionally. Any SSH session using SSH-RSA is subject to brown out (failure during random time periods). Please use rsa-sha2-256 or rsa-sha2-512 instead. For more details see https://aka.ms/ado-ssh-rsa-deprecation. remote: ERROR_SSH_UNSUPPORTED_CIPHER (7)."

------------------------------
João Caparroz
------------------------------

Hello Svetlana, thank you for your response.

Can you tell me if, because of this problem, it has been affecting some ENDPOINTS of the REST itself?
Whenever I try to create a new push plan using ENDPOINT: GitPush, REST does not create a push plan ID, making it impossible to upload objects to git.
Can you tell me if there is any relationship?

Thanks!

Hi João,

We're aware of that problem (especially with Git Azure) and producing the fixes quickly.

The PA on-premises v 11 is going to receive the fix shortly this month, following with fixes for v12.

Best regards,

Hello, great day!

I'm trying to make new Git requests within the TM1 REST and I'm receiving an error warning me of the depreciation of my SSH. However, this deprecation is not true, as my ssh was updated to the latest possible, as indicated by Microsoft itself (https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/comment-page-2/#comments). Anyone suffering from the same problem? Any solution? Or can we accept that this is just an update bug?

Thanks!

Error message:
"TM1 Git failed to connect to remote. Reason: remote: Command git-upload-pack: You're using ssh-rsa that is about to be deprecated and your request has been blocked intentionally. Any SSH session using SSH-RSA is subject to brown out (failure during random time periods). Please use rsa-sha2-256 or rsa-sha2-512 instead. For more details see https://aka.ms/ado-ssh-rsa-deprecation. remote: ERROR_SSH_UNSUPPORTED_CIPHER (7)."

------------------------------
João Caparroz
------------------------------

Hello João,

Unfortunately this is a critical issue for Azure repository and you need to deploy our fix asap. It affects all the Git endpoint to tm1, even if you're not using Workbench, for Azure repos.

However, you should be able to use ecdsa and ed25519 instead - not supported by Azure but good with GitHub.

Best regards,

Hello Svetlana, thank you for your response.

Can you tell me if, because of this problem, it has been affecting some ENDPOINTS of the REST itself?
Whenever I try to create a new push plan using ENDPOINT: GitPush, REST does not create a push plan ID, making it impossible to upload objects to git.
Can you tell me if there is any relationship?

Thanks!

Hi João,

We're aware of that problem (especially with Git Azure) and producing the fixes quickly.

The PA on-premises v 11 is going to receive the fix shortly this month, following with fixes for v12.

Best regards,

Hello, great day!

I'm trying to make new Git requests within the TM1 REST and I'm receiving an error warning me of the depreciation of my SSH. However, this deprecation is not true, as my ssh was updated to the latest possible, as indicated by Microsoft itself (https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/comment-page-2/#comments). Anyone suffering from the same problem? Any solution? Or can we accept that this is just an update bug?

Thanks!

Error message:
"TM1 Git failed to connect to remote. Reason: remote: Command git-upload-pack: You're using ssh-rsa that is about to be deprecated and your request has been blocked intentionally. Any SSH session using SSH-RSA is subject to brown out (failure during random time periods). Please use rsa-sha2-256 or rsa-sha2-512 instead. For more details see https://aka.ms/ado-ssh-rsa-deprecation. remote: ERROR_SSH_UNSUPPORTED_CIPHER (7)."

------------------------------
João Caparroz
------------------------------