Skip to content

Oxalis extension to support unsigned SignalMessage Error responses and pass as exception with description

Notifications You must be signed in to change notification settings

dladlk/oxalis-as4-unsigned-error

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 

Repository files navigation

oxalis-as4-unsigned-error module

Purpose

Drop this jar into your Oxalis-AS4 classpath and activate it to see unencrypted rejection messages from server access point

Idea

The OxalisUnsignedSignalErrorResponseModule tries to add to the default CXF Bus an InIntercepter:

https://github.com/dladlk/oxalis-as4-unsigned-error/blob/main/src/main/java/network/oxalis/as4/outbound/OxalisUnsignedSignalErrorResponseInInterceptor.java#L39-L99

In handleFault it checks if raised exception is PolicyException with texts "Soap Body is not SIGNED" AND "The received token does not match the token inclusion requirement", SignalMessage is not empty and has an Error filled in - and throws OxalisUnsignedSignalErrorResponseException with the contents from the first SignalMessage.Error of a SOAP Fault.

Installation

Copy jar to classpath and activate by adding to your reference.conf or oxalis.conf:


oxalis.module.as4.unsigned = {
    class = network.oxalis.as4.outbound.OxalisUnsignedSignalErrorResponseModule
}

About

Oxalis extension to support unsigned SignalMessage Error responses and pass as exception with description

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages