Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1330

Track Last Logon for Each User, Generate Reports of Inactive or Least Active Users

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • User Console
    • None
    • 11

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - 19 April 2019

      Hello everyone,

      We’re happy to say that we have delivered Early Access Program for License Usage monitoring in Crowd.

      You can find more details here: https://confluence.atlassian.com/crowd/license-usage-center-by-crowd-data-center-at-atlassian-summit-2019-las-vegas-968680984.html

      Best regards,

      Marek Radochonski
      Senior Product Manager, Crowd
      mradochonski@atlassian.com

      Please track the last logon for each user. This is crucial for managing the user base and removing inactive users. Please generate reports of least active or inactive users. This helps admins keep their user base clean. With hard limits to number of users, and many admins creating users, it's important to remove users that aren't active to free up space for more users.

      Thank you.

            [CWD-1330] Track Last Logon for Each User, Generate Reports of Inactive or Least Active Users

            Marek Radochonski (Inactive) added a comment -

            Hello everyone,

            We’re happy to say that we have delivered Early Access Program for License Usage monitoring in Crowd.

            You can find more details here: https://confluence.atlassian.com/crowd/license-usage-center-by-crowd-data-center-at-atlassian-summit-2019-las-vegas-968680984.html

            Best regards,

            Marek Radochonski
            Senior Product Manager, Crowd

            Marek Radochonski (Inactive) added a comment - Hello everyone, We’re happy to say that we have delivered Early Access Program for License Usage monitoring in Crowd. You can find more details here: https://confluence.atlassian.com/crowd/license-usage-center-by-crowd-data-center-at-atlassian-summit-2019-las-vegas-968680984.html Best regards, Marek Radochonski Senior Product Manager, Crowd

            DaveT added a comment -

            The lastAuthenticated attribute appears to be set when a crowd internal directory is used for authentication. But when a delegated authentication directory is used, this attribute is not set.

            At our site, we have Jira, Confluence, Fisheye/Crucible, Bamboo and Stash all tied to a single crowd instance using a delegated authentication directory. We're trying to implement a process to identify and disable unused accounts, but none of these applications exposes the last login date/time through a REST api. As a result, we have to write queries directly against the application databases to get this information and to make matters worse none of them store the information in exactly the same way. This would be soooo much easier if Crowd would just keep track of the lastAuthenticated attribute for us. Even if Crowd didn't expose it through the REST api, we'd at least have one database to look at instead of eight (we have multiple instances of some of the products).

            DaveT added a comment - The lastAuthenticated attribute appears to be set when a crowd internal directory is used for authentication. But when a delegated authentication directory is used, this attribute is not set. At our site, we have Jira, Confluence, Fisheye/Crucible, Bamboo and Stash all tied to a single crowd instance using a delegated authentication directory. We're trying to implement a process to identify and disable unused accounts, but none of these applications exposes the last login date/time through a REST api. As a result, we have to write queries directly against the application databases to get this information and to make matters worse none of them store the information in exactly the same way. This would be soooo much easier if Crowd would just keep track of the lastAuthenticated attribute for us. Even if Crowd didn't expose it through the REST api, we'd at least have one database to look at instead of eight (we have multiple instances of some of the products).

            John McHugh added a comment -

            This would be a great feature - one that I was surprised was not already implemented from day 1?

            John McHugh added a comment - This would be a great feature - one that I was surprised was not already implemented from day 1?

            Seth Ladd added a comment -

            This issue originated from https://support.atlassian.com/browse/CWDSUP-1430

            Seth Ladd added a comment - This issue originated from https://support.atlassian.com/browse/CWDSUP-1430

              Unassigned Unassigned
              cd124e9d5fb7 Seth Ladd
              Votes:
              12 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: