VisualSVN Server supports Integrated Windows Authentication. With this feature clients are able to authenticate to the server with their current Windows credentials. In other words, a domain user gains access to the server without being prompted to provide his username and password. Comparison of authentication methods available in VisualSVN Server is given in the KB39 article.
In order to enable Integrated Windows Authentication in VisualSVN Server, perform the following steps:
- Start the VisualSVN Server Manager console.
- Click Action | Properties.
- Click the Authentication tab.
- Click the Use Windows authentication option and select the Integrated Windows Authentication check box.
- Click the OK button.
VisualSVN HTTP Service will restart, and the domain users will automatically authenticate with their current Windows credentials.
The main recommendations are as follows:
- It is recommended to upgrade your Subversion clients to the latest stable release.
- To prevent passwords from being cached on disk it is recommended to disable Basic authentication.
Integrated Windows Authentication in VisualSVN Server is designed to work out-of-the-box. But nevertheless, under some circumstances Single Sign-On may not work. Here is the list of the most frequent cases:
- MS Edge and Chrome enable Single Sign-On by default only for sites belonging to the Local intranet zone. If you access the server by its fully qualified domain name (FQDN), the web browser may not recognize the server as belonging to Local intranet and will not enable Single Sign-On for it. Consider the article KB239 for resolution steps.
- Single Sign-On is disabled by default in Mozilla Firefox. You are requested to explicitly add your server to the whitelist of trusted sites. Consider the KB42 article.
- Internet Explorer allows Single Sign-On only to local intranet sites. Consider KB41 to learn more about Internet Explorer behavior and workarounds.
- Eclipse IDE may require additional configuration to use Single Sign-On. Consider the KB145 article for resolution steps.
- Single Sign-On may fail if you run VisualSVN HTTP Service under a dedicated user account. This happens when you don't have Service Principal Name (SPN) configured properly for a dedicated user account. The issue and resolution are described in the article KB52.
Note that Integrated Windows Authentication is only available with the Enterprise license. So you will be requested to enter a license key. You can request a free evaluation license from the evaluation page.