Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9726

Incorrect permission class-name should throw exception at runtime

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 7.1.0.DR14
    • Security
    • Hide

      Add non-existent permission into default-permission-mapper:

      /subsystem=elytron/constant-permission-mapper=default-permission-mapper:write-attribute(name=permissions[4],value={class-name=WrongName})

      and use this mapper at runtime. No exception is thrown.

      Show
      Add non-existent permission into default-permission-mapper: /subsystem=elytron/constant-permission-mapper= default -permission-mapper:write-attribute(name=permissions[4],value={ class- name=WrongName}) and use this mapper at runtime. No exception is thrown.

    Description

      In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2565 Incorrect permission class-name should throw exception at runtime

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12932 Upgrade WildFly Core to 4.0.1.Final

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3796 Incorrect Elytron permission class-name or module should throw exception

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

          Task - Represents a small unit of work that is not end-user facing. WFCORE-3596 further improve the permissions mapping configuration model to be manageable to by a tool

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              rhn-support-ivassile Ilia Vassilev
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: