Saving plaintext passwords was intentionally disabled in svn starting from version 1.12. There's no configuration key to re-enable this feature. The only way to make Subversion save your password as a plain text is to enable it at the compile time.

However, Subversion is still able to read the plaintext passwords.
And there's an official script to manually save your password as a plain text.

1. Consider removing any edits from ~/.subversion/config and ~/.subversion/servers. Just remove both files if in doubt.
2. Use your svn server at least once (e.g. checkout something).
   Verify and permanantly accept the server server certificate fingerprint, if asked.
   This would generate ~/.subversion/auth/svn.simple/xxxxx file (where "xxxxx" is some hash), but there would be no password in it yet.
3. Run svn auth and note the
   Authentication realm: <https://myserver.mydomain:12345> VisualSVN Server string in the output.
4. Use the official workaround script to store your password as plaintext:

wget https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/store-plaintext-password.py
chmod +x store-plaintext-password.py
./store-plaintext-password.py -u your_username "<https://myserver.mydomain:12345> VisualSVN Server"

5. doublecheck that ~/.subversion/auth/svn.simple/xxxxx now actually contains your password
6. chmod 600 ~/.subversion/auth/svn.simple/xxxxx
7. try using your svn server again (e.g. svn update).

Just tested on svn version 1.14.1 (r1886195), installed with simply apt install subversion, on Ubuntu 22.

Saving plaintext passwords was intentionally disabled in svn starting from version 1.12. There's no configuration key to re-enable this feature. The only way to make Subversion save your password as a plain text is to enable it at the compile time.

However, Subversion is still able to read the plaintext passwords.
And there's an official script to manually save your password as a plain text.

1. Consider removing any edits from ~/.subversion/config and ~/.subversion/servers. Just remove both files if in doubt.
2. Use your svn server at least once (e.g. checkout something).
   Verify and permanantly accept the server server certificate fingerprint, if asked.
   This would generate ~/.subversion/auth/svn.simple/xxxxx file (where "xxxxx" is some hash), but there would be no password in it yet.
3. Run svn auth and note the
   Authentication realm: <https://myserver.mydomain:12345> VisualSVN Server string in the output.
4. Use the official workaround script to store your password as plaintext:

wget https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/store-plaintext-password.py
chmod +x store-plaintext-password.py
./store-plaintext-password.py -u your_username "<https://myserver.mydomain:12345> VisualSVN Server"

5. doublecheck that ~/.subversion/auth/svn.simple/xxxxx now actually contains your password
6. chmod 600 ~/.subversion/auth/svn.simple/xxxxx (just-in-case)
7. chmod 700 ~/.subversion/auth/svn.simple (just-in-case)
8. try using your svn server again (e.g. svn update).

Just tested on svn version 1.14.1 (r1886195), installed with simply apt install subversion, on Ubuntu 22.

Saving plaintext passwords was intentionally disabled in svn starting from version 1.12. There's no configuration key to re-enable this feature. The only way to make Subversion save your password as a plain text is to enable it at the compile time.

However, Subversion is still able to read the plaintext passwords.
And there's an official script to manually save your password as a plain text.

1. Consider removing any edits from ~/.subversion/config and ~/.subversion/servers. Just remove both files if in doubt.
2. Use your svn server at least once (e.g. checkout something).
   Verify and permanantly accept the server server certificate fingerprint, if asked.
   This would generate ~/.subversion/auth/svn.simple/xxxxx file (where "xxxxx" is some hash), but there would be no password in it yet.
3. Run svn auth and note the
   Authentication realm: <https://myserver.mydomain:12345> VisualSVN Server string in the output.
4. Use the official workaround script to store your password as plaintext:

wget https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/store-plaintext-password.py
chmod +x store-plaintext-password.py
./store-plaintext-password.py -u your_username "<https://myserver.mydomain:12345> VisualSVN Server"

5. doublecheck that ~/.subversion/auth/svn.simple/xxxxx now actually contains your password
6. chmod 700 ~/.subversion/auth/svn.simple/xxxxx
7. chmod 700 ~/.subversion/auth/svn.simple
8. try using your svn server again (e.g. svn update).

Just tested on svn version 1.14.1 (r1886195), installed with simply apt install subversion, on Ubuntu 22.

Saving plaintext passwords was intentionally disabled in svn starting from version 1.12. There's no configuration key to re-enable this feature. The only way to make Subversion save your password as a plain text is to enable it at the compile time.

However, Subversion is still able to read the plaintext passwords.
And there's an official script to manually save your password as a plain text.

1. Consider removing any edits from ~/.subversion/config and ~/.subversion/servers. Just remove both files if in doubt.
2. Use your svn server at least once (e.g. checkout something).
   Verify and permanantly accept the server server certificate fingerprint, if asked.
   This would generate ~/.subversion/auth/svn.simple/xxxxx file (where "xxxxx" is some hash), but there would be no password in it yet.
3. Run svn auth and note the
   Authentication realm: <https://myserver.mydomain:12345> VisualSVN Server string in the output.
4. Use the official workaround script to store your password as plaintext:

wget https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/store-plaintext-password.py
chmod +x store-plaintext-password.py
./store-plaintext-password.py -u your_username "<https://myserver.mydomain:12345> VisualSVN Server"

5. doublecheck that ~/.subversion/auth/svn.simple/xxxxx now actually contains your password
6. chmod 600 ~/.subversion/auth/svn.simple/xxxxx
7. try using your svn server again (e.g. svn update).

Just tested on svn version 1.14.1 (r1886195), installed with simply apt install subversion, on Ubuntu 22.