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

Allow CROWD to Automatically Unlock accounts after X minutes

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 2
    • 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.

      Problem Statement:

      In JIRA, after three unsuccessful login attempts a user is locked out of the account.

      Requirement

      Automatically the account become active for a user afer 15 mins.

            [CWD-4973] Allow CROWD to Automatically Unlock accounts after X minutes

            It's good feature else Administrator has to be available 24X7 on call to unlock users. Self unlock is best option. Don't know why this still not taken, as it major feature not picked from 3 years. 

            Vijayaraya Sagar added a comment - It's good feature else Administrator has to be available 24X7 on call to unlock users. Self unlock is best option. Don't know why this still not taken, as it major feature not picked from 3 years. 

            pshukla2 added a comment -

            Please add this feature, so we can configure auto-unlock time. It will save us development time in making our own solution to do this.

            pshukla2 added a comment - Please add this feature, so we can configure auto-unlock time. It will save us development time in making our own solution to do this.

            Can we get this one implemented? We can bulk unlock which is great but if they get locked someone has to manually unlock it which is not ideal. Unlocking the account after a configurable amount of minutes we can just say well wait 30 min and try again taking the burden from administration.

            Dave Brewer added a comment - Can we get this one implemented? We can bulk unlock which is great but if they get locked someone has to manually unlock it which is not ideal. Unlocking the account after a configurable amount of minutes we can just say well wait 30 min and try again taking the burden from administration.

            It has been open since 2017 and no one looking. Any updates that we could get on this one?

            Nilotpol Patgiri added a comment - It has been open since 2017 and no one looking. Any updates that we could get on this one?

            I'm surprised that given the functionality in Crowd, to in effect implement password requirements and complexity that would be implemented if integrated with LDAP, that this is not of a higher priority.  It just seems that Atlassian implementations not part of LDAP are one feature away from fully comparable password management functionality.

             

            I would suggest that the lockout interval be selectable.  Perhaps "15m, 30m, 45m 1h, 12h 24h, never" options.

             

            Hoping and watching!

             

            Paul J. Hecker added a comment - I'm surprised that given the functionality in Crowd, to in effect implement password requirements and complexity that would be implemented if integrated with LDAP, that this is not of a higher priority.  It just seems that Atlassian implementations not part of LDAP are one feature away from fully comparable password management functionality.   I would suggest that the lockout interval be selectable.  Perhaps "15m, 30m, 45m 1h, 12h 24h, never" options.   Hoping and watching!  

            Can you please change the priority of ticket from Low to High?

            Umesh Kanaujia added a comment - Can you please change the priority of ticket from Low to High?

            pshukla2 added a comment -

            Please add functionality in CROWD, where we can configure to lock a user after 3 or 'x' number of unsuccessful login attempts (incorrect password) and auto-unlock after 'Y' number of minutes (e.g. 15 minutes).

            pshukla2 added a comment - Please add functionality in CROWD, where we can configure to lock a user after 3 or 'x' number of unsuccessful login attempts (incorrect password) and auto-unlock after 'Y' number of minutes (e.g. 15 minutes).

              Unassigned Unassigned
              bmcelveen Branden McElveen (Inactive)
              Votes:
              20 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated: