Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1874

Inconsistent access control response structures

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 8.0.0.Beta1
    • None
    • Management
    • None

    Description

      Compare the access control meta data for the different rrd() requests:

      a) https://gist.github.com/heiko-braun/6229507
      b) https://gist.github.com/heiko-braun/6229497

      It happens on a system with two datasources confgured (ExampleDS & Test). You can find the server config attached to this issues.

      What we are looking for is a reliable response structure, without any ambiguity.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users HAL-38 Access Control Support

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Feature Request - Feature requests from customers and/or users WFLY-490 Domain Management Role Based Access Control

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users WFLY-1900 Register override model for DS and RA regardless of if enabled or not

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kkhan1@redhat.com Kabir Khan
              rhn-support-hbraun Heiko Braun
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: