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

Test for JBEAP-19640, JBEAP-19641 SSLConfiguratorImplTest fails on ibm-java-1.8

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 7.3.2.CR1
    • Test Suite
    • None

    Description

      Test org.wildfly.security.ssl.SSLConfiguratorImplTest.testRejectNonExistentCipherSuite for issues https://issues.redhat.com/browse/JBEAP-19640 and https://issues.redhat.com/browse/JBEAP-19641 fail with EAP version 7.3.2.GA-CR1 on AssertionError at org.wildfly.security.ssl.SSLConfiguratorImplTest.testRejectNonExistentCipherSuite(SSLConfiguratorImplTest.java:56).

      Trace log:

      10:50:45,522 FINE  (main) [javax.security.sasl] <null:-1> IBMSASL Build-Level: -20150506
10:50:45,666 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm SSL
10:50:45,698 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLS
10:50:45,698 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLSV1
10:50:45,699 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLSV1.1
10:50:45,699 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLSV1.2
10:50:45,699 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm SSL_TLS
10:50:45,700 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm SSL_TLSV2
10:50:45,700 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm DEFAULT
10:50:45,704 TRACE (main) [org.wildfly.security] <SSLUtils.java:125> Supported protocols are: [TLSV1.2, TLSV1.1, TLSV1]
10:50:45,705 TRACE (main) [org.wildfly.security] <SSLUtils.java:139> Attempting to get an SSLContext instance using protocol TLSV1.2 and provider IBMJSSE2 version 1.8
10:50:46,714 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm SSL
10:50:46,715 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLS
10:50:46,716 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLSV1
10:50:46,717 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLSV1.1
10:50:46,718 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm TLSV1.2
10:50:46,720 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm SSL_TLS
10:50:46,720 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm SSL_TLSV2
10:50:46,721 TRACE (main) [org.wildfly.security] <SSLUtils.java:115> Provider IBMJSSE2 version 1.8 was added for algorithm DEFAULT
10:50:46,723 TRACE (main) [org.wildfly.security] <SSLUtils.java:125> Supported protocols are: [TLSV1.2, TLSV1.1, TLSV1]
10:50:46,724 TRACE (main) [org.wildfly.security] <SSLUtils.java:139> Attempting to get an SSLContext instance using protocol TLSV1.2 and provider IBMJSSE2 version 1.8

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19640 (7.3.z) ELY-1979 - Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19641 (7.3.z) ELY-1981 - SSL Module missing plugin configuration to assemble multi-version jar

          • 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

          Activity

            People

              Unassigned Unassigned
              dcihak@redhat.com Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: