u/pc/rhodecode-enterprise-ce-fork-pc Files · docs/admin/repo-perm-steps.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

             repo-perm-steps.rst
        
                    45 lines
            
             | 2.0 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / admin / repo-perm-steps.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      .. _set-repo-perms:

      Setting Repository Permissions

      ------------------------------

      To set the permissions on an individual |repo|, use the following steps:

      1. Open :menuselection:`Admin --> Repositories` and select

         :guilabel:`edit` beside the |repo| you wish to configure.

      2. On the |repo| settings page you will see a number of tabs. Exploring these

         you will find the following main configuration options for a |repo|.

      3. Once you make changes, select :guilabel:`Save`

      * :guilabel:`Repository group`: Lets you to add a |repo| to a |repo| group.

      * :guilabel:`Owner`: Lets you change the |repo| owner. Useful when users are

        moving roles within an organisation.

      * :guilabel:`Enable automatic locking`: For more information,

        see :ref:`repo-locking`

      * :guilabel:`User Access`: On the permissions tab you can add users,

        or user groups, and set the permissions each has for that |repo|.

      * :guilabel:`Invalidate repository cache`: On the Caches tab you can delete

        the |repo| cache, sometimes needed when mirroring.

      .. _set-repo-group-perms:

      Setting Repository Group Permissions

      ------------------------------------

      To set the permissions on a Repository Group, use the following steps:

      1. Open :menuselection:`Admin --> Repository groups` and select

         :guilabel:`edit` beside the |repo| you wish to configure.

      2. On the |repo| group settings page you will see a number of tabs. Exploring

         these you will find the following main configuration options:

      * :guilabel:`Owner`: Lets you change the group owner. Useful when users are

        moving roles within an organisation.

      * :guilabel:`Group parent`: Lets you add the |repo| group as a sub-group

        of a larger group, i.e. :guilabel:`QA-Repos >> QA-Repos-Berlin`

      * :guilabel:`Enable automatic locking`: For more information,

        see :ref:`repo-locking`

      * :guilabel:`User Access`: On the permissions tab you can add users,

        or user groups, and set the permissions each has for that |repo| group.

      * :guilabel:`Add Child Group`: Allows you to add sub-repository-groups

        that will all share the same permissions.

	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	.. _set-repo-perms:

		Setting Repository Permissions
		------------------------------

		To set the permissions on an individual \|repo\|, use the following steps:

		1. Open :menuselection:`Admin --> Repositories` and select
		:guilabel:`edit` beside the \|repo\| you wish to configure.
		2. On the \|repo\| settings page you will see a number of tabs. Exploring these
		you will find the following main configuration options for a \|repo\|.
		3. Once you make changes, select :guilabel:`Save`

		* :guilabel:`Repository group`: Lets you to add a \|repo\| to a \|repo\| group.
		* :guilabel:`Owner`: Lets you change the \|repo\| owner. Useful when users are
		moving roles within an organisation.
		* :guilabel:`Enable automatic locking`: For more information,
		see :ref:`repo-locking`
		* :guilabel:`User Access`: On the permissions tab you can add users,
		or user groups, and set the permissions each has for that \|repo\|.
		* :guilabel:`Invalidate repository cache`: On the Caches tab you can delete
		the \|repo\| cache, sometimes needed when mirroring.

		.. _set-repo-group-perms:

		Setting Repository Group Permissions
		------------------------------------

		To set the permissions on a Repository Group, use the following steps:

		1. Open :menuselection:`Admin --> Repository groups` and select
		:guilabel:`edit` beside the \|repo\| you wish to configure.
		2. On the \|repo\| group settings page you will see a number of tabs. Exploring
		these you will find the following main configuration options:

		* :guilabel:`Owner`: Lets you change the group owner. Useful when users are
		moving roles within an organisation.
		* :guilabel:`Group parent`: Lets you add the \|repo\| group as a sub-group
		of a larger group, i.e. :guilabel:`QA-Repos >> QA-Repos-Berlin`
		* :guilabel:`Enable automatic locking`: For more information,
		see :ref:`repo-locking`
		* :guilabel:`User Access`: On the permissions tab you can add users,
		or user groups, and set the permissions each has for that \|repo\| group.
		* :guilabel:`Add Child Group`: Allows you to add sub-repository-groups
		that will all share the same permissions.