Details

    • Bug Priority:
      Category 1
    • ACT Numbers:

      40659

      Description

      On 4.0.c community, on startup from fresh new install, using lucene index

      Using authentication.chain=authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap

      ldap auth and sync activated

      On users admin console (http://localhost:8081/share/page/console/admin-console/users)

      • Create a new User
      • Edit user : check "Disable Account"

      Result : the user details still displays : "Account Status: Enabled", still this user cannot connect (wich is expected)

      This is a minor visual issue, the problem is : there seems to be no user friendly way to reenable this account, maybe because the UI "thinks" the user is already enabled ?

      Another consequence wich is a lot more critical is that external user created through site invitation are created disabled, and are not enabled when accepting invitation.
      (https://issues.alfresco.com/jira/browse/ALF-12036)

      After invitation accept :

      On Share admin ui : "Account Status: Enabled"
      On user://alfrescoUserStore/sys:system/sys:people/cm:user_login -> usr:enabled = false
      On workspace://SpacesStore/sys:system/sys:people/cm:user_login -> cm:personDisabled aspect

      Expected result :
      User should be enabled when accepting invitation (InviteHelper.java/acceptNominatedInvitation).
      [...]
      if (false==authenticationService.getAuthenticationEnabled(invitee))

      { authenticationService.setAuthenticationEnabled(invitee, true); }

      [...]

      This doesn't seems to work as expected, I suspect "authenticationService.getAuthenticationEnabled()" return true even if the user is disabled :

      I've done some javascript test :

      var sq =

      { query : "+ASPECT:\"cm:personDisabled\"", language : "lucene" }

      ;
      sr = search.query(sq);
      for each (p in sr)

      { print(people.isAccountEnabled(p.properties["userName"])); }

      this return a bunch of "true" wich is inconsistant (cm:personDisabled aspect is set so user isAccountEnabled should only return "false" in this case)

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedbugs Closed Bugs (Inactive)
                  Reporter:
                  jvanluyten Julien Van Luyten (Inactive)
                • Votes:
                  3 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 40 minutes
                    40m

                      Structure Helper Panel