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

Elytron revise why exception stacktrace is not logged in some cases

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.ER2
    • 7.1.0.DR19
    • Security
    • None

    Description

      During verification of JBEAP-9297 I have found another occurences where logging should be justified.
      In some cases not logging exception can hide original cause of problem.

      But justification is necessary if extending loggin won't introduce unnecessary logs, however does not seems to me this should be case.

      [mchoma@localhost wildfly-elytron]$ grep -r ".*\.debug([^\"]" --include=*.java .
./src/main/java/org/wildfly/security/auth/realm/FileSystemSecurityRealm.java:                ElytronMessages.log.debug(e);
./src/main/java/org/wildfly/security/auth/realm/FileSystemSecurityRealm.java:                            ElytronMessages.log.debug(e);
./src/main/java/org/wildfly/security/auth/realm/FileSystemSecurityRealm.java:                ElytronMessages.log.debug(e);
./src/main/java/org/wildfly/security/auth/realm/FileSystemSecurityRealm.java:                                    ElytronMessages.log.debug(e);
./src/main/java/org/wildfly/security/http/util/SecurityProviderServerMechanismFactory.java:                            log.debug(e);
./src/main/java/org/wildfly/security/http/util/SecurityProviderServerMechanismFactory.java:                            log.debug(e);
./src/main/java/org/wildfly/security/http/util/ServiceLoaderServerMechanismFactory.java:                log.debug(e);
./src/main/java/org/wildfly/security/http/util/ServiceLoaderServerMechanismFactory.java:                log.debug(e);
./src/main/java/org/wildfly/security/sasl/util/SecurityProviderSaslClientFactory.java:                            log.debug(e);
./src/main/java/org/wildfly/security/sasl/util/SecurityProviderSaslClientFactory.java:                            log.debug(e);
./src/main/java/org/wildfly/security/sasl/util/SecurityProviderSaslServerFactory.java:                                log.debug(e);
./src/main/java/org/wildfly/security/sasl/util/SecurityProviderSaslServerFactory.java:                            log.debug(e);

[mchoma@localhost wildfly-elytron]$ grep -r ".*\.trace([^\"]" --include=*.java .
./src/main/java/org/wildfly/security/ssl/CipherSuiteSelector.java:            ElytronMessages.tls.trace(b);
./src/main/java/org/wildfly/security/ssl/CipherSuiteSelector.java:                    ElytronMessages.tls.trace(b);
./src/main/java/org/wildfly/security/http/impl/DigestAuthenticationMechanism.java:                        log.trace(e);

      These are OK

      ./src/main/java/org/wildfly/security/ssl/CipherSuiteSelector.java:            ElytronMessages.tls.trace(b);
./src/main/java/org/wildfly/security/ssl/CipherSuiteSelector.java:                    ElytronMessages.tls.trace(b);

      Setting to Critical priority, as this could reveal useful information during process of troubleshooting.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ELY-1233 Elytron revise why exception stacktrace is not logged in some cases

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11459 Upgrade WildFly Elytron to 1.1.0.Beta54

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9297 Elytron, log cause of LoginException during obtaining kerberos ticket

          • 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

          Activity

            People

              rhn-engineering-lgao Lin Gao
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified