Keep your private tokens secret. Anyone with access to them can interact with some part of
GitLab as if they were you.
.col-lg-8.private-tokens-reset
=renderpartial: 'reset_token',locals: {label: 'RSS token',button_label: 'Reset RSS token',help_text: 'Your RSS token is used to access your personalized RSS feeds without username/password authentication. It cannot be used to access any other data.'}
-ifincoming_email_token_enabled?
=renderpartial: 'reset_token',locals: {label: 'Incoming email token',button_label: 'Reset incoming email token',help_text: 'Your incoming email token is used to authenticate you when creating new issues by email, and is included in your project-specific email addresses. It cannot be used to access any other data.'}
Keep this token secret. Anyone who gets ahold of it can read activity and issue RSS feeds as if they were you.
You should
=link_to'reset it',[:reset,:rss_token,:profile],method: :put,data: {confirm: 'Are you sure? Any RSS URLs currently in use will stop working.'}
if that ever happens.
-ifincoming_email_token_enabled?
%hr
.row.prepend-top-default
.col-lg-4.profile-settings-sidebar
%h4.prepend-top-0
Incoming email token
%p
Your incoming email token is used to authenticate you when you create a new issue by email, and is included in your personal project-specific email addresses.
Keep this token secret. Anyone who gets ahold of it can create issues as if they were you.
You should
=link_to'reset it',[:reset,:incoming_email_token,:profile],method: :put,data: {confirm: 'Are you sure? Any issue email addresses currently in use will stop working.'}