search

tfsaggregator / tfsaggregator-webhooks

WARNING: the team is no more maintaing this version. See aggreggator-cli instead.
https://github.com/tfsaggregator/aggregator-cli
19 stars 22 forks source link

Failed to communicate with TFS #15

Closed mbendtsen closed 5 years ago

mbendtsen commented 6 years ago

I am trying to install TFS aggregator as a Web Service version 2.3.

I have setup the WebApplication on IIS. First I did it using HTTP. Then when trying to configure the service hook it told me to use HTTPS if using Basic Authentication. Then I set up SSL for TFS Aggregator., but using a self-made certificate. Get the following error message: The remote certificate is invalid according to the validation procedure. Is there any solution where I do not use Basic Authentication? Or do I have to use a trusted certificate?

jessehouwing commented 6 years ago

You can install the self made cert in the trusted certs store of the user or machine.

On 9 Jan 2018 14:07, "Michael Bendtsen" notifications@github.com wrote:

I am trying to install TFS aggregator as a Web Service version 2.3.

I have setup the WebApplication on IIS. First I did it using HTTP. Then when trying to configure the service hook it told me to use HTTPS if using Basic Authentication. Then I set up SSL for TFS Aggregator., but using a self-made certificate. Get the following error message: The remote certificate is invalid according to the validation procedure. Is there any solution where I do not use Basic Authentication? Or do I have to use a trusted certificate?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tfsaggregator/tfsaggregator-webhooks/issues/15, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS0ZmQTk6W1qecHSazsHgHdI-fPekks5tI2R5gaJpZM4RXzH0 .

mbendtsen commented 6 years ago

Okay, finally got this to work. Now I am back to the Basic authentication requires a secure connection to the server error.

These are my steps:

  1. Created self-signed certificate and added to trusted cert
  2. Assigned certificate to the site in IIS
  3. SSL Settings: Require SSL
  4. Added DNS name from certificate in hosts file
  5. When opening 'https:///api/workitem' it does not complain about certificate anymore.
  6. Updated Service Hool with the new https URL.

TFS does not run using SSL. It that the issue?

jessehouwing commented 6 years ago

Yes, tfs must run over SSL. Otherwise it won't open up the basic auth to allow PAT access, though in theory we should be able to make it use NTLM / Kernersville on-prem, that's not how the system is setup at the moment.

On 11 Jan 2018 10:33, "Michael Bendtsen" notifications@github.com wrote:

Okay, finally got this to work. Now I am back to the Basic authentication requires a secure connection to the server error.

These are my steps:

  1. Created self-signed certificate and added to trusted cert
  2. Assigned certificate to the site in IIS
  3. SSL Settings: Require SSL
  4. Added DNS name from certificate in hosts file
  5. When opening 'https:///api/workitem' it does not complain about certificate anymore.
  6. Updated Service Hool with the new https URL.

TFS does not run using SSL. It that the issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tfsaggregator/tfsaggregator-webhooks/issues/15#issuecomment-356877852, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS2V9FBfed8eaapJHr_74j2N-K68_ks5tJdVjgaJpZM4RXzH0 .