u/pc/rhodecode-enterprise-ce-fork-pc Files · docs/admin/setting-repo-perms.rst

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

Download file

             setting-repo-perms.rst
        
                    26 lines
            
             | 880 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / admin / setting-repo-perms.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      .. _permissions-info-add-group-ref:

      Repository Administration

      =========================

      Repository permissions in |RCM| can be managed in a number of different ways.

      This overview should give you an insight into how you could adopt particular

      settings for your needs:

      * Global |repo| permissions: This allows you to set the default permissions

        for each new |repo| created within |RCM|, see :ref:`repo-default-ref`. All

        |repos| created will inherit these permissions unless explicitly configured.

      * Individual |repo| permissions: To set individual |repo| permissions,

        see :ref:`set-repo-perms`.

      * Repository Group permissions: This allows you to define the permissions for

        a group, and all |repos| created within that group will inherit the same

        permissions.

      .. toctree::

          repo-perm-steps

          repo-extra-fields

          repo-hooks

          repo-issue-tracker

          repo-vcs

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

marcink project: added all source files and assets	r1	.. _permissions-info-add-group-ref:

		Repository Administration
		=========================

		Repository permissions in \|RCM\| can be managed in a number of different ways.
		This overview should give you an insight into how you could adopt particular
		settings for your needs:

		* Global \|repo\| permissions: This allows you to set the default permissions
		for each new \|repo\| created within \|RCM\|, see :ref:`repo-default-ref`. All
		\|repos\| created will inherit these permissions unless explicitly configured.
		* Individual \|repo\| permissions: To set individual \|repo\| permissions,
		see :ref:`set-repo-perms`.
		* Repository Group permissions: This allows you to define the permissions for
		a group, and all \|repos\| created within that group will inherit the same
		permissions.

		.. toctree::

		repo-perm-steps
		repo-extra-fields
		repo-hooks
		repo-issue-tracker
		repo-vcs