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

Crowd Clients may delete Crowd administrators, to the point where there are no Crowd administrators

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Authentication / Security, Core features
    • Operating System: CentOS 5.3, x86-32
      JDK: Sun JDK 1.6 6u16 32bit
      PostgreSQL Server: 8.3.8-1 32bit
      PostgreSQL JDBC: 8.4-701

      Browser: Mozilla Firefox 3.5.3 on Mac OS X 10.6 Snow Leopard

    • 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.

      A Crowd client, such as confluence; can delete users from Crowd. This includes the Admin users, regardless of what groups these admin users are in.

      Once all the admin users are deleted, you can no longer administer Crowd.

            [CWD-1720] Crowd Clients may delete Crowd administrators, to the point where there are no Crowd administrators

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3551058 ] New: JAC Suggestion Workflow 3 [ 3629169 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Parent Original: CWD-1182 [ 71613 ]
            Affects Version/s Original: 2.0.1 [ 14670 ]
            Workflow Original: JAC Sub-task Workflow [ 3389509 ] New: JAC Suggestion Workflow [ 3551058 ]
            Issue Type Original: Sub-task [ 6 ] New: Suggestion [ 10000 ]
            Priority Original: Low [ 4 ]
            Status Original: Closed [ 6 ] New: RESOLVED [ 5 ]
            set-jac-bot made changes -
            Link New: This issue is detailed by CWD-1182 [ CWD-1182 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1510104 ] New: JAC Sub-task Workflow [ 3389509 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392883 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1510104 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273552 ] New: Simplified Crowd Development Workflow v2 [ 1392883 ]
            jawong.adm made changes -
            Workflow Original: JIRA Bug Workflow v2 [ 184969 ] New: Crowd Development Workflow v2 [ 273552 ]
            Justin Koke made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            David O'Flynn [Atlassian] made changes -
            Parent New: CWD-1182 [ 71613 ]
            Issue Type Original: Bug [ 1 ] New: Sub-task [ 6 ]
            David O'Flynn [Atlassian] made changes -
            Description Original: A Crowd client, such as confluence; can delete users from Crowd. This includes the Admin users, regardless of what groups these admin users are in.

            Once all the admin users are deleted, you can no longer administer Crowd.

            With respect to Dragons, the documentation leads the user in to only creating one Crowd administrator, which could easily be deleted by an administrator of any one of the clients, irrespective of their crowd administration credentials.             		New: A Crowd client, such as confluence; can delete users from Crowd. This includes the Admin users, regardless of what groups these admin users are in.

            Once all the admin users are deleted, you can no longer administer Crowd.

            Priority Original: Blocker [ 1 ] New: Minor [ 4 ]
            Security Original: Reporters and Developers [ 10071 ]

              Unassigned Unassigned
              pdzwart PdZ (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: