##// END OF EJS Templates
u » pc » rhodecode-enterprise-ce-fork-pc
RSS

Fork of rhodecode-enterprise-ce

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.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r2203:8a18c3c3 default
Show More
default-user-perms.rst
31 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / admin / default-user-perms.rst
History | Annotation | Raw |Copy content |Copy permalink

Default User Permissions

There are two ways in which the default user settings work:

System-wide Level

On a system-wide level, you can set the default user permissions so that all new users are given a certain set of permissions unless individually tailored, or added to a user group. For more information about system-wide default permissions, see the :ref:`permissions-info-anon-ref` and :ref:`permissions-default-ref` sections.

User Group Level

On a user group level, you can set the default user settings for the user group, and all users within that group will get those default permissions unless individually tailored. For more information about setting default permissions for all the different entities, see the :ref:`permissions-default-ref` section.

For more detailed information about managing the different permissions settings, see the following sections:

  • :ref:`permissions-info-anon-ref`
  • :ref:`permissions-add-user`
  • :ref:`permissions-default-ref`
  • :ref:`permissions-info-add-group-ref`