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

caches: use individual namespaces per user to prevent beaker caching problems....

caches: use individual namespaces per user to prevent beaker caching problems. - especially for mysql in case large number of data in caches there could be critical errors storing cache, and thus preventing users from authentication. This is caused by the fact that we used single namespace for ALL users. It means it grew as number of users grew reaching mysql single column limit. This changes the behaviour and now we use namespace per-user it means that each user-id will have it's own cache namespace fragmenting maximum column data to a single user cache. Which we should never reach.

marcink - - Load All Authors

File last commit:

r2122:de425417 default


                r2572:5b07455a

default

Download file

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

        marcink
    
permissions: expose new view that lists all available views for usage in whitelist access.

              r1943
            
      <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

        marcink
    
white-list-access: improved UI.

              r2122
            
      Currently the following views are set:

        marcink
    
permissions: expose new view that lists all available views for usage in whitelist access.

              r1943
            
      </p>

        marcink
    
white-list-access: improved UI.

              r2122
            
      <pre>

        marcink
    
permissions: expose new view that lists all available views for usage in whitelist access.

              r1943
            
      % for entry in c.whitelist_views:

      ${entry}

      % endfor

        marcink
    
white-list-access: improved UI.

              r2122
            
      </pre>

        marcink
    
permissions: expose new view that lists all available views for usage in whitelist access.

              r1943
            
          </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>

        marcink
    
white-list-access: improved UI.

              r2122
            
                  <td class="td-x">

                      % if active:

                          ${h.bool2icon(active)}

                      % endif

                  </td>

        marcink
    
permissions: expose new view that lists all available views for usage in whitelist access.

              r1943
            
                  <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

marcink permissions: expose new view that lists all available views for usage in whitelist access.	r1943

		<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
marcink white-list-access: improved UI.	r2122	Currently the following views are set:
marcink permissions: expose new view that lists all available views for usage in whitelist access.	r1943	</p>

marcink white-list-access: improved UI.	r2122	<pre>
marcink permissions: expose new view that lists all available views for usage in whitelist access.	r1943	% for entry in c.whitelist_views:
		${entry}
		% endfor
marcink white-list-access: improved UI.	r2122	</pre>
marcink permissions: expose new view that lists all available views for usage in whitelist access.	r1943
		</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>
marcink white-list-access: improved UI.	r2122	<td class="td-x">
		% if active:
		${h.bool2icon(active)}
		% endif
		</td>
marcink permissions: expose new view that lists all available views for usage in whitelist access.	r1943	<td class="td-x">${view_fqn}</td>
		<td class="td-x" title="${route_name}">${view_url}</td>
		</tr>
		% endfor
		</table>
		</div>

		</div>
		</div>