Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
72:subversion_limitations [2018/07/09 17:27] – [Known Limitations] bkkr72:subversion_limitations [2018/08/02 15:24] – [Known Limitations] bkkr
Line 3: Line 3:
 ====== Known Limitations ====== ====== Known Limitations ======
  
-Known limitations that affect all Subversion servers+Known limitations that affect all Subversion servers<font inherit/inherit;;inherit;;inherit></font>
  
-^Title^Description^Workarounds| +**Supported Server Versions**
-|Supported Server Versions|1.2.X, 1.3.X, 1.4.X, 1.5.X, 1.6.X, 1.7.X, 1.8.X|N/A| +
-|HTTP option request must trigger authentication|In order to validate user credentials the Subversion server must enforce authentication (<font inherit/Courier New,Courier,monospace;;inherit;;inherit>valid-user</font><font inherit/Arial,Helvetica,sans-serif;;inherit;;inherit>) for HTTP Option requests</font>|N/A| +
-|Supported authentication schemes|Only HTTP Basic, HTTP Digest, and NTLM are supported authentication schemes.|N/A| +
-|Supported protocols|Only Subversion servers that can be reached via http<font inherit/Arial,Helvetica,sans-serif;;inherit;;inherit>or</font><font inherit/Courier New,Courier,monospace;;inherit;;inherit>https</font><font inherit/Arial,Helvetica,sans-serif;;inherit;;inherit>are</font><font inherit/Arial,Helvetica,sans-serif;;inherit;;inherit>supported.</font>|N/A| +
-|Shown labels in Stages|Stages will not show labels that correspond to Subversion tags or branches.|N/A| +
-|Access to repositories|System account requires full read and write access to the repository.|N/A| +
-|Subversion auto:properties|As Stages only operates on the documents/files in the Subversion repository, directories/folders are not checked and therefore no support for auto:properties is available.|A few auto:properties use-cases can be implemented through special configuration settings in the PKitConfig.xml. Please contact the Stages-Support to see whether your use-case can be achieved.|+
  
-\\+   * Description: 1.2.X, 1.3.X, 1.4.X, 1.5.X, 1.6.X, 1.7.X, 1.8.X 
 +  * Workarounds: N/A 
 + 
 + \\ **HTTP option request must trigger authentication** 
 +  * Description: In order to validate user credentials, the Subversion server must enforce authentication (<font inherit/Courier New,Courier,monospace;;inherit;;inherit>valid-user</font>) for HTTP Option requests 
 +  * Workarounds: N/A 
 + 
 + \\ **Supported authentication schemes** 
 +  * Description: Only HTTP Basic, HTTP Digest, and NTLM are supported authentication schemes 
 +  * Workarounds: N/A 
 + 
 + \\ **Supported protocols** 
 +  * Description: Only Subversion servers that can be reached via HTTP or HTTPS are supported 
 +  * Workarounds: N/A 
 + 
 + \\ **Shown labels in Stages** 
 +  * Description: Stages will not show labels that correspond to Subversion tags or branches 
 +  * Workarounds: N/A 
 + 
 +**Access to repositories** 
 +  * Description: System accounts require full read and write access to the repository 
 +  * Workarounds: N/A 
 + 
 +**Subversion auto:properties** 
 +  * Description: As Stages only operates on the documents/files in the Subversion repository, directories/folders are not checked and therefore no support for auto:properties is available 
 +  * Workarounds: A few auto:properties use-cases can be implemented through special configuration settings in the PKitConfig.xml. Please contact the Stages-Support to see whether your use-case can be achieved