0

I want to create Self-signed-certificate in TFS so that my build agent can connect to TFS (which it can't currently Err. "Basic authentication Requires a secure connection to server"). I have read that in order to create a self signed certificate and host the tfs using HTTPS, "TFS Configuration Wizard" creates two self signed certificates. But the problem I cant find TFS Configuration Wizard anywhere I believe it runs while installation is in progress but how can I now access it and create the certificates? All help is appreciated .

muhammad qasim
  • 21
  • 2

1 Answers1

0

You can remove the Application Server feature as the screenshot below, then reconfigure it:

enter image description here

Cece Dong - MSFT
  • 29,631
  • 1
  • 24
  • 39
  • Thanks for the reply but I don't see how it will help me in this case. I want to connect from build machine to TFS server and having the error that "basic authentication requires a secure connection" I don't see it can help me in this regard. – muhammad qasim Apr 09 '18 at 07:05
  • You've mentioned in your post "the problem I cant find TFS Configuration Wizard anywhere I believe it runs while installation is in progress but how can I now access it and create the certificates". – Cece Dong - MSFT Apr 09 '18 at 07:10
  • Check this link about how to run the agent with self-signed certificate to see whether it helps you: https://learn.microsoft.com/en-us/vsts/build-release/actions/agents/certificate?view=tfs-2018 – Cece Dong - MSFT Apr 09 '18 at 07:11
  • yes only if I can access it afterwards then I can create Self signed certificates. for the creation of self signed certificates every thread I have read has referred to the configuration wizard – muhammad qasim Apr 09 '18 at 11:46
  • What you want is configure application tier, so try to remove this feature and reconfigure it (my screenshot shows), you'll see the configuration wizard. – Cece Dong - MSFT Apr 10 '18 at 08:56
  • thanks for the help but I wont be able to do so due to other project dependencies . I have solved the problem with another workaround – muhammad qasim Apr 11 '18 at 09:12
  • I ended up changing the authentication type I am no more using PAT – muhammad qasim Apr 12 '18 at 07:38