-
Notifications
You must be signed in to change notification settings - Fork 27
Authentication
Eugene Bekker edited this page Feb 26, 2017
·
1 revision
Tug itself does not provide authentication per se (aside from node registration); neither does the original Microsoft pull server. However, you can apply whatever authentication your web server permits. For example, IIS can be configured to demand client certificate authentication. Nodes do send client certificate information (a self-signed certificate with a 1-year life) on registration, so you could potentially capture that information, and then configure your web server to allow future access attempts from that client.