[BSERV-4117] Provide authentication dates on the administration GUI

Type: Suggestion
Resolution: Fixed
Fix Version/s: 3.7.0
Component/s: Administration - Users and Groups, Enterprise, User Profiles
Labels:
None

Feedback Policy:

We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Problem Definition

For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates,

Workaround

Until Stash 3.7 was released, that is currently only possible by querying directly the database as described on the KB below (with the exception of "Delegated LDAP users"):

Query for inactive or idle users.

Implementation

Stash 3.7 will include a last authentication time in the UI regardless of which directory type they belong to. It is important to notice that the timestamp is also included in the REST payload for /rest/api/latest/admin/users. Hence, there is no more need to query the database.

For example:

$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{  
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[  
      {  
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{  
            "self":[  
               {  
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {  
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{  
            "self":[  
               {  
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {  
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{  
            "self":[  
               {  
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}

Important info:

This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.

Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.

duplicates

BSERV-4070 Last authentication login details

Closed

is incorporated by

BSERV-5168 Show more details for Stash users on the UI

Gathering Interest

mentioned in: Page No Confluence page found with the given URL.; Page No Confluence page found with the given URL.; Page No Confluence page found with the given URL.; Wiki Page Loading...; Page Loading...

(2 mentioned in)

Renata Dornelas made changes - 27/Jan/2025 5:52 PM

Remote Link

Original: This issue links to "Page (Atlassian Documentation)" [ 122732 ]

Francisco Crespo Smith made changes - 22/Aug/2023 10:23 AM

Assignee

Original: Francisco Crespo Smith [ d001924c850a ]

Francisco Crespo Smith made changes - 22/Aug/2023 9:40 AM

Assignee

New: Francisco Crespo Smith [ d001924c850a ]

Katherine Yabut made changes - 19/Sep/2019 5:50 AM

Workflow	Original: JAC Suggestion Workflow [ 3398095 ]	New: JAC Suggestion Workflow 3 [ 3625072 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]

Monique Khairuliana (Inactive) made changes - 21/Aug/2019 12:51 AM

Workflow

Original: BSERV Suggestions Workflow [ 3392385 ]

New: JAC Suggestion Workflow [ 3398095 ]

Monique Khairuliana (Inactive) made changes - 21/Aug/2019 12:27 AM

Workflow	Original: Stash Workflow - Restricted [ 1447915 ]	New: BSERV Suggestions Workflow [ 3392385 ]
Issue Type	Original: Story [ 16 ]	New: Suggestion [ 10000 ]
Priority	Original: Low [ 4 ]
Status	Original: Closed [ 6 ]	New: Resolved [ 5 ]

Owen made changes - 07/Jul/2016 4:05 AM

Workflow

Original: Stash Workflow [ 584369 ]

New: Stash Workflow - Restricted [ 1447915 ]

ThiagoBomfim (Inactive) made changes - 16/Dec/2015 2:22 AM

Description

Original: h3. Problem Definition

For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates,

h3. Workaround
Until Stash 3.7 was released, that is currently only possible by querying directly the database as described on the KB below:
- [Query for inactive or idle users|https://confluence.atlassian.com/display/BitbucketServerKB/Query+for+inactive+or+idle+users].

h3. Implementation

Stash 3.7 will include a last authentication time in the UI. The timestamp is also included in the [REST payload|https://developer.atlassian.com/static/rest/stash/3.11.3/stash-rest.html#idp1173568] for {{/rest/api/latest/admin/users}}. For example:
{code}
$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[
      {
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}{code}

{panel}
(i) *Important info:*

This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.

Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.
{panel}

New: h3. Problem Definition

For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates,

h3. Workaround
Until Stash 3.7 was released, that is currently only possible by querying directly the database as described on the KB below (with the exception of "Delegated LDAP users"):
- [Query for inactive or idle users|https://confluence.atlassian.com/display/BitbucketServerKB/Query+for+inactive+or+idle+users].

h3. Implementation

Stash 3.7 will include a last authentication time in the UI _regardless of which directory type they belong to_. It is important to notice that the timestamp is also included in the [REST payload|https://developer.atlassian.com/static/rest/stash/3.11.3/stash-rest.html#idp1173568] for {{/rest/api/latest/admin/users}}. Hence, there is no more need to query the database.

For example:
{code}
$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[
      {
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}{code}

{panel}
(i) *Important info:*

This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.

Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.
{panel}

ThiagoBomfim (Inactive) made changes - 16/Dec/2015 2:19 AM

Description

Original: h3. Problem Definition

For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates,

h3. Workaround
Until Stash 3.7 was released, that is currently only possible by querying directly the database as described on the KB below:
- [Query for inactive or idle users|https://confluence.atlassian.com/display/BitbucketServerKB/Query+for+inactive+or+idle+users].]

h3. Implementation

Stash 3.7 will include a last authentication time in the UI. The timestamp is also included in the [REST payload|https://developer.atlassian.com/static/rest/stash/3.11.3/stash-rest.html#idp1173568] for {{/rest/api/latest/admin/users}}. For example:
{code}
$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[
      {
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}{code}

{panel}
(i) *Important info:*

This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.

Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.
{panel}

New: h3. Problem Definition

For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates,

h3. Workaround
Until Stash 3.7 was released, that is currently only possible by querying directly the database as described on the KB below:
- [Query for inactive or idle users|https://confluence.atlassian.com/display/BitbucketServerKB/Query+for+inactive+or+idle+users].

h3. Implementation

Stash 3.7 will include a last authentication time in the UI. The timestamp is also included in the [REST payload|https://developer.atlassian.com/static/rest/stash/3.11.3/stash-rest.html#idp1173568] for {{/rest/api/latest/admin/users}}. For example:
{code}
$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[
      {
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}{code}

{panel}
(i) *Important info:*

This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.

Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.
{panel}

ThiagoBomfim (Inactive) made changes - 16/Dec/2015 2:18 AM

Description

Original: For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates, but that is currently only possible [through the database|https://confluence.atlassian.com/display/STASHKB/Query+for+inactive+or+idle+users].

Please provide this data on the administration GUI in an easy-to-order format.

*Implementation:*

Stash 3.7 will include a last authentication time in the UI. That time will also be included in the [REST payload|https://developer.atlassian.com/static/rest/stash/3.11.3/stash-rest.html#idp1173568] for {{/rest/api/latest/admin/users}}. For example:
{code}
$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[
      {
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}{code}
This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.
Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.

New: h3. Problem Definition

For licensing purposes, Stash administrators sometimes want to delete/deactivate users that have not used their account ever (or for a very long time in fact). For this, they would need to see these login dates,

h3. Workaround
Until Stash 3.7 was released, that is currently only possible by querying directly the database as described on the KB below:
- [Query for inactive or idle users|https://confluence.atlassian.com/display/BitbucketServerKB/Query+for+inactive+or+idle+users].]

h3. Implementation

Stash 3.7 will include a last authentication time in the UI. The timestamp is also included in the [REST payload|https://developer.atlassian.com/static/rest/stash/3.11.3/stash-rest.html#idp1173568] for {{/rest/api/latest/admin/users}}. For example:
{code}
$ curl -H "Content-Type:application/json" --user admin:admin -H "Accept:application/json" -X GET http://localhost:7990/bitbucket/rest/api/1.0/admin/users

{
   "size":3,
   "limit":25,
   "isLastPage":true,
   "values":[
      {
         "name":"admin",
         "emailAddress":"admin@example.com",
         "id":1,
         "displayName":"Administrator",
         "active":true,
         "slug":"admin",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1450221817844,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/admin"
               }
            ]
         }
      },
      {
         "name":"user",
         "emailAddress":"user@example.com",
         "id":2,
         "displayName":"User",
         "active":true,
         "slug":"user",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user"
               }
            ]
         }
      },
      {
         "name":"user2",
         "emailAddress":"user@2.com",
         "id":51,
         "displayName":"User 2",
         "active":true,
         "slug":"user2",
         "type":"NORMAL",
         "directoryName":"Bitbucket Internal Directory",
         "deletable":true,
         "lastAuthenticationTimestamp":1449467319385,
         "mutableDetails":true,
         "mutableGroups":true,
         "links":{
            "self":[
               {
                  "href":"http://localhost:7990/bitbucket/users/user2"
               }
            ]
         }
      }
   ],
   "start":0
}{code}

{panel}
(i) *Important info:*

This information can't be gleaned retroactively, so it will be maintained from the upgrade on. Until a user first logs in after the upgrade their last timestamp will show as "Unknown" in the UI.

Each time a user authenticates via HTTP or SSH (including accessing a Git repository over HTTP or SSH, push or pull), or via the login page, their timestamp will be updated. If a user selects "Remember me" on the login screen, each time their session times out (generally ~30 minutes of inactivity unless reconfigured), when they get a new session using their remember me token their timestamp will also be updated.
{panel}

Assignee:: Unassigned

Reporter:: Peter Koczan (Inactive)

Votes:: 27 Vote for this issue

Watchers:: 23 Start watching this issue

Created:: 20/Nov/2013 1:29 PM

Updated:: 27/Jan/2025 5:52 PM

Resolved:: 29/Jan/2015 4:58 AM

Bitbucket Data Center

Details

Description

Problem Definition

Workaround

Implementation

Attachments

Issue Links

Forms

Activity

People

Dates

Backbone Issue Sync