rhodecode-enterprise-ce Files · rhodecode/templates/admin/permissions/permissions_auth_token_access.mako

goto-switcher: optimized performance and query capabilities....

goto-switcher: optimized performance and query capabilities. - Previous implementation had on significant bug. The use of LIMIT 20 was limiting results BEFORE auth checks. In case of large ammount of similarly named repositories user didn't had access too, the result goto search was empty. This was becuase first 20 items fetched didn't pass permission checks and final auth list was empty. To fix this we now use proper filtering for auth using SQL. It means we first check user allowed repositories, and add this as a filter so end result from database is already to only the accessible repositories.

marcink - - Load All Authors

File last commit:

r1943:089c11e9 default


                r2038:2bdf9d4d

default

Download file

             permissions_auth_token_access.mako
        
                    61 lines
            
             | 1.6 KiB
            
                | application/x-mako
            
             |
                MakoHtmlLexer
            
             / rhodecode / templates / admin / permissions / permissions_auth_token_access.mako
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      <div class="panel panel-default">

        <div class="panel-heading">

            <h3 class="panel-title">${_('View whitelist')}</h3>

        </div>

        <div class="panel-body">

          <div class="">

      <p class="pr-description">

      View white list defines a set of views that can be accessed using auth token without the need to login.

      Adding ?auth_token = SECRET_TOKEN to the url authenticates this request as if it

      came from the the logged in user who owns this authentication token.

      E.g. adding `RepoFilesView.repo_file_raw` allows to access a raw diff using such url:

          http[s]://server.com/{repo_name}/raw/{commit_id}/{file_path}?auth_token=SECRET_TOKEN

      White list can be defined inside `${c.whitelist_file}` under `${c.whitelist_key}=` setting

      Currently under this settings following views are set:

      </p>

          <pre>

      % for entry in c.whitelist_views:

      ${entry}

      % endfor

          </pre>

          </div>

        </div>

      </div>

      <div class="panel panel-default">

        <div class="panel-heading">

            <h3 class="panel-title">${_('List of views available for usage in whitelist access')}</h3>

        </div>

        <div class="panel-body">

          <div class="">

            <table class="rctable ip-whitelist">

              <tr>

                  <th>Active</th>

                  <th>View FQN</th>

                  <th>URL pattern</th>

              </tr>

              % for route_name, view_fqn, view_url, active in c.view_data:

              <tr>

                  <td class="td-x">${h.bool2icon(active)}</td>

                  <td class="td-x">${view_fqn}</td>

                  <td class="td-x" title="${route_name}">${view_url}</td>

              </tr>

              % endfor

            </table>

          </div>

        </div>

      </div>

	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



				<div class="panel panel-default">
				<div class="panel-heading">
				<h3 class="panel-title">${_('View whitelist')}</h3>
				</div>
				<div class="panel-body">
				<div class="">

				<p class="pr-description">
				View white list defines a set of views that can be accessed using auth token without the need to login.
				Adding ?auth_token = SECRET_TOKEN to the url authenticates this request as if it
				came from the the logged in user who owns this authentication token.

				E.g. adding `RepoFilesView.repo_file_raw` allows to access a raw diff using such url:
				http[s]://server.com/{repo_name}/raw/{commit_id}/{file_path}?auth_token=SECRET_TOKEN

				White list can be defined inside `${c.whitelist_file}` under `${c.whitelist_key}=` setting

				Currently under this settings following views are set:
				</p>

				<pre>
				% for entry in c.whitelist_views:
				${entry}
				% endfor
				</pre>

				</div>

				</div>
				</div>


				<div class="panel panel-default">
				<div class="panel-heading">
				<h3 class="panel-title">${_('List of views available for usage in whitelist access')}</h3>
				</div>
				<div class="panel-body">
				<div class="">


				<table class="rctable ip-whitelist">
				<tr>
				<th>Active</th>
				<th>View FQN</th>
				<th>URL pattern</th>
				</tr>

				% for route_name, view_fqn, view_url, active in c.view_data:
				<tr>
				<td class="td-x">${h.bool2icon(active)}</td>
				<td class="td-x">${view_fqn}</td>
				<td class="td-x" title="${route_name}">${view_url}</td>
				</tr>
				% endfor
				</table>
				</div>

				</div>
				</div>