This is an old revision of the document!
Known Limitations
Known limitations that affect all Subversion servers
Title | Description | Workarounds |
---|---|---|
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. |