2017-08-17 10:53:50 -04:00
- breadcrumb_title "Access Tokens"
2016-04-15 03:36:44 -04:00
- page_title "Personal Access Tokens"
2017-06-22 10:47:50 -04:00
- @content_class = "limit-container-width" unless fluid_layout
2017-08-01 04:50:59 -04:00
2016-04-15 03:36:44 -04:00
.row.prepend-top-default
2017-06-22 10:47:50 -04:00
.col-lg-4.profile-settings-sidebar
2016-04-15 03:36:44 -04:00
%h4.prepend-top-0
= page_title
%p
2016-06-02 23:37:37 -04:00
You can generate a personal access token for each application you use that needs access to the GitLab API.
2016-08-10 20:04:25 -04:00
%p
2016-08-17 18:21:18 -04:00
You can also use personal access tokens to authenticate against Git over HTTP.
They are the only accepted password when you have Two-Factor Authentication (2FA) enabled.
2016-08-10 20:04:25 -04:00
2017-06-22 10:47:50 -04:00
.col-lg-8
2017-12-03 23:01:18 -05:00
- if @new_personal_access_token
2016-06-09 23:19:05 -04:00
.created-personal-access-token-container
2016-06-09 04:38:49 -04:00
%h5.prepend-top-0
Your New Personal Access Token
.form-group
2018-03-25 09:50:09 -04:00
.input-group
= text_field_tag 'created-personal-access-token', @new_personal_access_token, readonly: true, class: "form-control js-select-on-focus", 'aria-describedby' => "created-personal-access-token-help-block"
2018-04-12 16:49:37 -04:00
%span.input-group-append
2018-04-12 18:55:40 -04:00
= clipboard_button(text: @new_personal_access_token, title: "Copy personal access token to clipboard", placement: "left", class: "input-group-text btn-default btn-clipboard")
2018-04-11 14:26:37 -04:00
%span#created-personal-access-token-help-block.form-text.text-muted.text-danger Make sure you save it - you won't be able to access it again.
2016-06-09 04:38:49 -04:00
%hr
2016-06-01 22:57:47 -04:00
2017-03-01 11:59:03 -05:00
= render "shared/personal_access_tokens_form", path: profile_personal_access_tokens_path, impersonation: false, token: @personal_access_token, scopes: @scopes
2016-04-19 05:58:35 -04:00
2017-03-01 11:59:03 -05:00
= render "shared/personal_access_tokens_table", impersonation: false, active_tokens: @active_personal_access_tokens, inactive_tokens: @inactive_personal_access_tokens
2017-10-12 10:17:54 -04:00
%hr
.row.prepend-top-default
.col-lg-4.profile-settings-sidebar
%h4.prepend-top-0
2018-05-31 10:01:04 -04:00
Feed token
2017-10-12 10:17:54 -04:00
%p
2018-05-31 10:01:04 -04:00
Your feed token is used to authenticate you when your RSS reader loads a personalized RSS feed or when when your calendar application loads a personalized calendar, and is included in those feed URLs.
2017-10-12 10:17:54 -04:00
%p
It cannot be used to access any other data.
2018-05-31 10:01:04 -04:00
.col-lg-8.feed-token-reset
2018-07-19 18:11:31 -04:00
= label_tag :feed_token, 'Feed token', class: "label-bold"
2018-05-31 10:01:04 -04:00
= text_field_tag :feed_token, current_user.feed_token, class: 'form-control', readonly: true, onclick: 'this.select()'
2018-04-11 14:26:37 -04:00
%p.form-text.text-muted
2018-05-31 10:01:04 -04:00
Keep this token secret. Anyone who gets ahold of it can read activity and issue RSS feeds or your calendar feed as if they were you.
2017-10-12 10:17:54 -04:00
You should
2018-05-31 10:01:04 -04:00
= link_to 'reset it', [:reset, :feed_token, :profile], method: :put, data: { confirm: 'Are you sure? Any RSS or calendar URLs currently in use will stop working.' }
2017-10-12 10:17:54 -04:00
if that ever happens.
- if incoming_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.
%p
It cannot be used to access any other data.
.col-lg-8.incoming-email-token-reset
2018-07-19 18:11:31 -04:00
= label_tag :incoming_email_token, 'Incoming email token', class: "label-bold"
2017-10-12 10:17:54 -04:00
= text_field_tag :incoming_email_token, current_user.incoming_email_token, class: 'form-control', readonly: true, onclick: 'this.select()'
2018-04-11 14:26:37 -04:00
%p.form-text.text-muted
2017-10-12 10:17:54 -04:00
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.' }
if that ever happens.