bernardo-mg / mule-ws-security-soap-example Goto Github PK

It is not possible generating the Maven site due to dependencies issues.

It may require more time than the example is worth, but there is a newer Mule version and the project could be adapted to it.

If a parent POM is added then the project stops working.

The SAML WS flows do not have tests.

The encrypted WS flows do not have tests.

The SAML web services currently do not support the use of consumers. Find a way to use consumers on them.

Currently the messages which go through the consumer, both the received message and the sent one, are not being logged.

I can't find any way to log them directly, and the few examples about this just add loggers to all the possible protocols loggers.

For example, if the consumer sends the message through HTTP the examples use:

<AsyncLogger name="org.mule.module.http.internal.HttpMessageLogger" level="DEBUG"/>

Currently the consumers and CXF endpoints are in the same flows. This is confusing, as they seem to be the same type of endpoint. The consumers should be moved to their own flows.

Currently the password protected endpoints seem to be using a plain password scheme. There should be an endpoint using a digested password.

The EntityXmlToModelTransformer can be replaced by a Mule transformer, probably.

The secured messages which require an username should receive it as part of the message, instead of get is as part of the configuration.

The signed WS flows do not have tests.