Petals BC SOAP

Add a component configuration to toggle stacktrace printing

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 4.3.5
  • Fix Version/s: 4.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When an external caller accesses a SOAP service (a JBI Consumes) or accesses its WSDL, an error can be present respectively either in the SOAP response (SOAP Fault) or in the Jetty error page.

    There should be a configuration property named "public-stacktraces-enabled" to control stacktraces printing.
    It should be true by default.

    Show
    When an external caller accesses a SOAP service (a JBI Consumes) or accesses its WSDL, an error can be present respectively either in the SOAP response (SOAP Fault) or in the Jetty error page. There should be a configuration property named "public-stacktraces-enabled" to control stacktraces printing. It should be true by default.
  • Environment:
    -

Issue Links

Activity

Victor NOËL made changes - Wed, 16 Sep 2015 - 11:38:05 +0200
Field Original Value New Value
Priority Blocker [ 1 ]
Description When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "disablePublicStacktraces" to disable stacktraces printing.
When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "disable-public-stacktraces" to disable stacktraces printing.
Victor NOËL made changes - Wed, 16 Sep 2015 - 13:48:57 +0200
Description When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "disable-public-stacktraces" to disable stacktraces printing.
When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "enable-public-stacktraces" to control stacktraces printing.
Victor NOËL made changes - Wed, 16 Sep 2015 - 14:06:26 +0200
Link This issue depends on PETALSBCSOAP-158 [ PETALSBCSOAP-158 ]
Victor NOËL made changes - Wed, 16 Sep 2015 - 14:06:40 +0200
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ] Minor [ 4 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Wed, 16 Sep 2015 - 14:06:44 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Wed, 16 Sep 2015 - 14:10:10 +0200
Summary Add a component or SU configuration to toggle stacktrace printing Add a component configuration to toggle stacktrace printing
Fix Version/s 4.4.0 [ 10405 ]
Description When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "enable-public-stacktraces" to control stacktraces printing.
When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "public-stacktraces-enabled" to control stacktraces printing.
Victor NOËL made changes - Wed, 16 Sep 2015 - 16:42:15 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Victor NOËL made changes - Wed, 16 Sep 2015 - 17:30:33 +0200
Description When an external caller access a SOAP service (a JBI Consumes), error can be present either in the SOAP response (soap fault) or in the Jetty error page.

There should be a configuration property named "public-stacktraces-enabled" to control stacktraces printing.
When an external caller accesses a SOAP service (a JBI Consumes) or accesses its WSDL, an error can be present respectively either in the SOAP response (SOAP Fault) or in the Jetty error page.

There should be a configuration property named "public-stacktraces-enabled" to control stacktraces printing.
It should be true by default.

People

Dates

  • Created:
    Wed, 16 Sep 2015 - 11:36:48 +0200
    Updated:
    Wed, 16 Sep 2015 - 17:30:33 +0200
    Resolved:
    Wed, 16 Sep 2015 - 16:42:15 +0200