Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-FINAL, 2.1
    • Fix Version/s: 2.2.0
    • Component/s: Security
    • Labels:
      None

      Description

      In J1 a user can be disabled but not a role or a group.
      I guess disabling users will be supported by J2 to allow migration from J1.

      I would also like to be able to disable Roles and Groups.
      It would allow for really advanced access management in J2 without it
      getting in the way for who doesn't need it (could even be hidden through configuration if needed).

      To have this standard available in J2 would be very nice for most large J2 implementations. Implementation itself would be quite easy and the gain enormous.

      Adding a boolean disabled attribute to o.a.j.security.BasePrincipal
      would do it (and of course BasePrincipalImpl and the object
      model behind it). The LoginModule, UserManager, GroupManager
      and RoleManager then can decide on this attribute if the Principal may
      be used (in isUserInRole(), isGroupInRole(), etc.)

      Original discussion about this issue:
      http://nagoya.apache.org/eyebrowse/ReadMsg?listId=22&msgNo=13265

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Vivek Kumar
            Reporter:
            Ate Douma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development