##// 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
adding-anonymous-user.rst
22 lines | 1018 B | text/x-rst | RstLexer
/ docs / admin / adding-anonymous-user.rst

Anonymous Users

By default, |RCM| provides |repo| access for registered users only. It can be configured to be world-open in terms of read and write permissions. This configuration is called "Anonymous Access" and allows |RCM| to be used as a public hub where unregistered users have access to your |repos|.

Anonymous access is useful for open source projects, universities, or if running inside a restricted internal corporate network to serve documents to all employees. Anonymous users get the default user permission settings that are applied across the whole |RCM| system.

To enable anonymous access to your |repos|, use the following steps:

  1. From the |RCM| interface, select :menuselection:`Admin --> Permissions`.
  2. On the Application tab, check the :guilabel:`Allow anonymous access` box.
  3. Select :guilabel:`Save`.
  4. To set the anonymous user access permissions, which are based on the default user settings, see :ref:`permissions-default-ref`.