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

Adding deployment permissions doesn't put server in requires reload state

    XMLWordPrintable

Details

    • Hide

      Steps to reproduce are described in JBEAP-416

      Show
      Steps to reproduce are described in JBEAP-416

    Description

      When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation doesn't require reload.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-416 Change in permissions is not visible until server reload

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-4898 Change in permissions is not visible until server reload

          • 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
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: