Changelog entry added, if necessary
Documentation created/updated
API support added
Tests added for this feature/bug
Review
- Has been reviewed by UX
- Has been reviewed by Frontend
- Has been reviewed by Backend
- Has been reviewed by Database
Conform by the merge request performance guides
Conform by the style guides
Squashed related commits together
Internationalization required/considered
End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?

## What does this MR do?

Adds an active sessions menu entry to the profile settings page. That page shows all the user's active sessions (aka logged in devices).

The user may revoke any unknown sessions.

## Are there points in the code the reviewer needs to double check?

## Why was this MR needed?

From a security standpoint it's relevant to be able to identify active sessions and revoke any of it.

The development of this MR is sponsored by @ siemens (/cc @bufferoverflow).

## Screenshots (if relevant)

![image](/uploads/c8f91efede6f461dda88287c3edcb5b5/image.png)

## Does this MR meet the acceptance criteria?

- [x] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [x] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [x] Tests added for this feature/bug
- Review
  - [x] Has been reviewed by UX
  - [ ] Has been reviewed by Frontend
  - [ ] Has been reviewed by Backend
  - [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
- [ ] Internationalization required/considered
- [ ] End-to-end tests pass (`package-and-qa` manual pipeline job)

## What are the relevant issue numbers?

Edited May 02, 2018 by Douwe Maan

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch "https://gitlab.com/siemens/gitlab-ce.git" "feature/display-active-sessions"
git checkout -b "siemens/gitlab-ce-feature/display-active-sessions" FETCH_HEAD

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout "origin/master"
git merge --no-ff "siemens/gitlab-ce-feature/display-active-sessions"

Step 4. Push the result of the merge to GitLab

git push origin "master"

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

Assignee

Assign to

10.8

Milestone

10.8

Assign milestone

Time tracking

5

Labels

Community contribution admin dashboard authentication backend frontend

Assign labels

View project labels

Reference: gitlab-org/gitlab-foss!17867

Cherry-pick this merge request

Pick into branch

Switch branch

Cancel

A new branch will be created in your fork and a new merge request will be started.

Next

Display and revoke active sessions

What does this MR do?

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?