Admin Token API: Identify Incoming Email Tokens
What does this MR do and why?
This MR adds support for identifying incoming email tokens to the Admin Token API.
References
- Issue: #512033 (closed)
- Epic: &15777
- Docs: https://docs.gitlab.com/ee/api/admin/token.html
MR acceptance checklist
checklist
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the javascript style guides -
Conforms to the database guides
How to set up and validate locally
-
You'll need to create a
personal access token
to access the token and get anincoming mail token
token that you'd like to query:-
Create a
personal access token
withadmin_mode
andapi
capabilities.Preferences > Access Tokens > Add a new token
- You'll need an incoming email token of a user. If you've seeded the GDK, you can get a token from an existing user in the
rails console
:
-
Create a
User.last.incoming_email_token
- Now you can retrieve information about this token:
curl -k --request POST \
--url 'https://gdk.test:3443/api/v4/admin/token' \
--header 'Authorization: Bearer <Admin Token from Step 2.1>' \
--header 'Content-Type: application/json' \
--data '{"token": "glimt-token-from-step-2.2"}'
{
"id": 68,
"username": "reported_user_22",
"name": "Diann Turcotte",
"state": "active",
...
}
Related to #512033 (closed)
Merge request reports
Activity
added Community contribution label
added groupauthentication typefeature labels
added Leading Organization label
added linked-issue label
added 1 commit
- c8d85f4c - Admin Token API: Identify Incoming Email Tokens
mentioned in issue #443597 (closed)
- Resolved by Isaac Durham
1 Message This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive. Documentation review
The following files require a review from a technical writer:
-
doc/api/admin/token.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Category Reviewer Maintainer backend @bhrai
(UTC+1)
@ahmed.hemdan
(UTC+1)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Danger Bot -
added backend documentation labels
added workflowready for review label
requested review from @shreyasagarwal
Hi
@jglassman1
! Please review this documentation merge request. This message was generated automatically. Improve it or delete it.added twtriaged label
requested review from @jglassman1
@shreyasagarwal @jglassman1, this Community contribution is ready for review.
- Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
- If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.
- Please ensure the group's Product Manager has validated the linked issue.
This message was generated automatically. Improve it or delete it.
Passing over to @idurham as he is the TW for groupauthentication now.
requested review from @idurham
removed review request for @jglassman1
added pipeline:mr-approved label
added pipelinetier-2 label
Hi
@idurham
,GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.
This message was generated automatically. Improve it or delete it.
added Technical Writing label
added 1221 commits
-
c8d85f4c...d86d1d09 - 1219 commits from branch
gitlab-org:master
- dd04b18a - Admin Token API: Identify Incoming Email Tokens
- 871852f9 - Admin Token API: Identify Incoming Email Tokens
-
c8d85f4c...d86d1d09 - 1219 commits from branch
reset approvals from @idurham by pushing to the branch
mentioned in issue gitlab-org/quality/triage-reports#21813 (closed)
- Resolved by Aboobacker MK
@tachyons-gitlab Could you please do the initial review as the expert of the auth domain? Thank you.
requested review from @tachyons-gitlab and removed review request for @shreyasagarwal
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
added 814 commits
-
871852f9...6b9e3d03 - 812 commits from branch
gitlab-org:master
- 602c7127 - Admin Token API: Identify Incoming Email Tokens
- dd71a40f - Admin Token API: Identify Incoming Email Tokens
-
871852f9...6b9e3d03 - 812 commits from branch
reset approvals from @tachyons-gitlab and @idurham by pushing to the branch
mentioned in epic gitlab-org#15777
mentioned in issue gitlab-org/quality/triage-reports#21889 (closed)
- Resolved by Aboobacker MK
@ahuntsman Could you review this MR as the backend maintainer ?
requested review from @ahuntsman
mentioned in issue gitlab-org/quality/triage-reports#21997 (closed)
added 2328 commits
-
dd71a40f...3f14b8f1 - 2326 commits from branch
gitlab-org:master
- aa567036 - Admin Token API: Identify Incoming Email Tokens
- a2aef147 - Admin Token API: Identify Incoming Email Tokens
-
dd71a40f...3f14b8f1 - 2326 commits from branch
reset approvals from @ahuntsman by pushing to the branch