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

Upgrade to Elytron Subsystem 1.0.0.Alpha20

    XMLWordPrintable

Details

    • Component Upgrade
    • Resolution: Done
    • Major
    • 7.1.0.DR11
    • None
    • Security
    • None

    Attachments

      Issue Links

        incorporates

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-6088 Inconsistency of resources *-ssl-context in model vs. XSD

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

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-7930 Coverity: dereference null value in ClassLoadingAttributeDefinitions (Elytron subsystem)

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

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-8369 Rename default-realm attribute in Elytron properties-realm

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

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-7926 Coverity: default platform encoding used in TokenRealmDefinition (Elytron subsystem)

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Verified

        Activity

          People

            darran.lofthouse@redhat.com Darran Lofthouse
            darran.lofthouse@redhat.com Darran Lofthouse
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: