MicroProfile Config properties are not taken into account by Jaeger client

I am trying to migrate tests from Thorntail test suite, both MP OpenTracing 1.0 and 1.3.

Let's have a simple Arquillian test with Jaeger containerized in Docker and a WAR-archive with CDI enabled (beans.xml) and META-INF/microprofile-config.properties included:

jaeger.sampler.param=1
jaeger.sampler.type=const

But it seems that Jaeger instance running in Docker does not take into account the properties defined in WAR's microprofile-config.properties file. It should trace every request to the deployed application but as far as I can see it does not.

Only manual instantiation and configuration of a Tracer object in @ApplicationScoped service leads to the expected behaviour. With @Inject 'ed tracer there is no success.

Regarding that let's imagine a user case: we have a deployment with @Traced annotated classes/methods, CDI enabled (beans.xml) and META-INF/microprofile-config.properties entries for Jaeger configuration. We don't want to modify existing classes (configuring existing tracer instance), we only want trace each REST request.

From reading the MP Config specs I expect Jaeger using my MP configuration properties (in case none of env or system variables JAEGER_* is set). Does it should work like this or am I missing something?