##// END OF EJS Templates
shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.

File last commit:

r2656:f7a8197c default
r2777:f1cc2e3d default
Show More
auth.rst
32 lines | 901 B | text/x-rst | RstLexer
project: added all source files and assets
r1 .. _authentication-ref:
Authentication Options
======================
docs: update LDAP documentation according to user feedback.
r2656 |RCE| provides a built in authentication against its own database. This is
implemented using ``rhodecode.lib.auth_rhodecode`` plugin. This plugin is
enabled by default.
Additionally, |RCE| provides a Pluggable Authentication System. This gives the
project: added all source files and assets
r1 administrator greater control over how users authenticate with the system.
.. important::
You can disable the built in |RCM| authentication plugin
``rhodecode.lib.auth_rhodecode`` and force all authentication to go
docs: update LDAP documentation according to user feedback.
r2656 through your authentication plugin of choice e.g LDAP only.
However, if you do this, and your external authentication tools fails,
you will be unable to access |RCM|.
project: added all source files and assets
r1
|RCM| comes with the following user authentication management plugins:
.. toctree::
docs: update LDAP documentation according to user feedback.
r2656 auth-ldap
auth-ldap-groups
auth-crowd
auth-pam
auth-token
project: added all source files and assets
r1 ssh-connection