@Tomek Mário Thank you for reaching out to Microsoft Q&A, unfortunately azuredeVops is not supported in Q&A forum. I would suggest you to raise/report your problem in azure deVops developer community here.
Unable to register self-hosted Azure DevOps Agent on MAC OS for Azure DevOps server with server certificate valid longer than 398 days.
How to register self-hosted Azure DevOps Agent on MAC OS pro Azure DevOps server with server certificate valid longer than 398 days.
Hello,
in our company, we are using for develop Azure DevOps server installed on our own servers. For the website of the Azure DevOps we have certificate valid for 5 years created by our own company. I wold like to register new self-hosted Agent on our MAC mini. But if i will try to register the Agent on MAC mini, I get this error:
"GET request to https://#DevOps_URI#/_apis/connectionData?connectOptions=1&lastChangeId=-1&lastChangeId64=-1 failed. System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception."
All stackTrace of the error is in the attachment:
268524-log.txt
I know, that this error returned because of new limits on trusted certificates for the MAC OS: https://support.apple.com/en-us/HT211025. If I change the server certificate for the Azure DevOps website to certificate with validity only for 397 days, so the registration of the Agent on MAC mini is succeeded. However, we would like to keep a server certificate valid for 5 years for the Azure DevOps website. Additionally, Apple's announcement states that "This change will not affect certificates issued from user-added or administrator-added Root CAs".
So is there any way how to register self-hosted Agent on the MAC OS for Azure DevOps with server certificate valid longer than 398 days?
Can you somebody help me please?
Community Center | Not monitored
2 answers
Sort by: Most helpful
-
VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator
2022-12-08T11:22:09.487+00:00 -
Tomek Mário 1 Reputation point
2022-12-08T12:03:16.1+00:00 @VenkateshDodda-MSFT Thank you for your response. So I posted a question in the DevOps developer community.