##// END OF EJS Templates
auth: don't break hashing in case of user with empty password....
auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.

File last commit:

r1:854a839a default
r2203:8a18c3c3 default
Show More
repo-locking.rst
14 lines | 586 B | text/x-rst | RstLexer

Repository Locking

Repository locking means that when a user pulls from a |repo|, only a push by that user will unlock it. This allows an Admin to pull from a |repo| and ensure that no changes can be introduced. You need Admin access to the |repo| to enable |repo| locking. To enable |repo| locking, use the following steps.

  1. From the |RCE| interface, select :menuselection:`Admin --> Repositories`, then :guilabel:`Edit` beside the |repo| you wish to lock.
  2. From the left-hand pane, select :menuselection:`Advanced --> Lock Repository`