Mendix authentication SOAP header mapper
Maps Mendix authentication credentials to/from web service SOAP headers.
SoapHeaderMapper
implementation that maps Mendix web service authentication SOAP headers to/from the emagiz_ws_mxauth message header. This mapping is only performed on request messages, as reply message don't contain authentication data.
The intended use for this header mapper is for 'proxying' authentication credentials from a web service hosted by eMagiz to a Mendix web service. Note that this does not provide an actual authentication mechanism to the eMagiz web service.
The source authentication SOAP header should have the following layout:
<exam:authentication xmlns:exam="http://www.example.org/"> <exam:username>username</exam:username> <exam:password>password</exam:password> </exam:authentication>
The three XML-elements in the example above can have any name and namespace, but the structure must be the same. The target SOAP header that is send to Mendix will always look the same (this is a fixed layout defined by Mendix); only the namespace is configurable.
Source authentication QName
Qualified name for the authentication SOAP header element of the inbound SOAP request message, e.g. {http://www.example.org/}authentication
.
Can be specified using any of the following syntax options:
localPart
{namespace}localPart
{namespace}prefix:localPart
Source username QName
Qualified name for the username element in the authentication SOAP header element of the inbound SOAP request message, e.g. {http://www.example.org/}username
.
Can be specified using any of the following syntax options:
localPart
{namespace}localPart
{namespace}prefix:localPart
Source password QName
Qualified name for the password element in the authentication SOAP header element of the inbound SOAP request message, e.g. {http://www.example.org/}password
.
Can be specified using any of the following syntax options:
localPart
{namespace}localPart
{namespace}prefix:localPart
Target namespace
Namespace for the Mendix authentication SOAP header element of the outbound SOAP request message, e.g. http://www.example.com/
.
Throw exception inbound
Whether to throw a SoapHeaderException
if the inbound SOAP request message is missing any of the required authentication data in the SOAP header.
Default is true
, which guarantees that all generated request messages will contain the emagiz_ws_mxauth message header. Disabling this will result in messages being created without this header (these cases are also logged as warnings).
Throw exception outbound
Whether to throw a SoapHeaderException
if the outbound request message is missing the required emagiz_ws_mxauth message header (or if the header value is incorrect).
Default is true
, which guarantees that all generated request SOAP messages will contain the Mendix authentication SOAP header. Disabling this will result in messages being created without this header (these cases are also logged as warnings).
Id
Name that uniquely identifies this flow component.
Required