Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
72:subversion_host_specific [2018/07/09 16:16]
bkkr [Host-Specific Configuration Properties]
72:subversion_host_specific [2018/08/02 16:35] (current)
bkkr [Host-Specific Configuration Properties]
Line 5: Line 5:
 Some properties can be defined per Subversion server, i.e. in a cms-host section. Some properties can be defined per Subversion server, i.e. in a cms-host section.
  
-^Property Name^Default Value^Description| +**User**
-|user| |You may enter the Subversion username for the Stages system account here instead of the corresponding field //Username //in the CMS profile. If both values exist, the username from the CMS profile is preferred. ​ | +
-|password| |You may enter the Subversion password for the Stages system account here instead of the corresponding field //Password //in the CMS profile. If both values exist, the password from the CMS profile is preferred. ​ | +
-|domain| |You may enter the Subversion default domain for the Stages system account, and all user accounts. (Only necessary for NTLM authentication) ​ | +
-|http.authentication.hostname (required for NTLM authentication)| |The host name of the server that runs Stages and is allowed to authenticate via NTLM against the Subversion server ​ | +
-|http.connection.timeout|300000|The timeout in milliseconds until a HTTP connection has to be established and the maximum period of inactivity (in milliseconds) between two consecutive data packets before the socket is closed. ​ | +
-|http.max.connections|100|The maximum number of simultaneously used HTTP connections between Stages and the Subversion Server. ​ | +
-|http.ssl.allow.all|false|When set to <font inherit/​Courier New,​Courier,​monospace;;​inherit;;​inherit>​true</​font>,​ disables any verification checks for certificates in case of SSL-secured HTTPS connections. It is recommended to only use this in test environments where no valid certificates exist (e.g. self-signed certificates).|+
  
-\\+   * Default Value: N/A 
 +  * Description:​ You may enter the Subversion username for the Stages system account here instead of the corresponding field Username in the CMS profile. If both values exist, the username from the CMS profile is preferred. 
 + 
 +**Password** 
 + 
 +  * Default Value: N/A 
 +  * Description:​ You may enter the Subversion password for the Stages system account here instead of the corresponding field Password in the CMS profile. If both values exist, the password from the CMS profile is preferred. 
 + 
 +**Domain** 
 + 
 +  * Default Value: N/A 
 +  * Description:​ You may enter the Subversion default domain for the Stages system account, and all user accounts. (Only necessary for NTLM authentication) 
 + 
 +**http.authentication.hostname ** (required for NTLM authentication) 
 + 
 +  * Default Value: N/A 
 +  * Description:​ The host name of the server that runs Stages and is allowed to authenticate via NTLM against the Subversion server 
 + 
 +**http.connection.timeout** 
 + 
 +  * Default Value: 300000 
 +  * Description:​ The timeout in milliseconds until a HTTP connection has to be established and the maximum period of inactivity (in milliseconds) between two consecutive data packets before the socket is closed. 
 + 
 +**http.max.connections** 
 + 
 +  * Default Value: 100 
 +  * Description:​ The maximum number of simultaneously used HTTP connections between Stages and the Subversion Server. 
 + 
 +**http.ssl.allow.all** 
 + 
 +  * Default Value: false 
 +  * Description:​ When set to <font inherit/​Courier New,​Courier,​monospace;;​inherit;;​inherit>​true</​font>,​ disables any verification checks for certificates in case of SSL-secured HTTPS connections. It is recommended to only use this in test environments where no valid certificates exist (e.g. self-signed certificates).