Chapter 9. Reference

9.1. Eclipse MicroProfile Config reference

9.1.1. Default Eclipse MicroProfile Config attributes

The Eclipse MicroProfile Config specification defines three ConfigSources by default.

ConfigSources are sorted according to their ordinal number. If a configuration must be overwritten for a later deployment, the lower ordinal ConfigSource is overwritten before a higher ordinal ConfigSource.

Table 9.1. Default Eclipse MicroProfile Config attributes


System properties


Environment variables


Property files META-INF/ found on the classpath


9.1.2. Eclipse MicroProfile Config SmallRye ConfigSources

The microprofile-config-smallrye project defines more ConfigSources you can use in addition to the default Eclipse MicroProfile Config ConfigSources.

Table 9.2. Additional Eclipse MicroProfile Config attributes


config-source in the Subsystem


ConfigSource from the Directory


ConfigSource from Class


An explicit ordinal is not specified for these ConfigSources. They inherit the default ordinal value found in the Eclipse MicroProfile Config specification.

9.2. Eclipse MicroProfile Fault Tolerance reference

9.2.1. Eclipse MicroProfile Fault Tolerance configuration properties

SmallRye Fault Tolerance specification defines the following properties in addition to the properties defined in the Eclipse MicroProfile Fault Tolerance specification.

Table 9.3. Eclipse MicroProfile Fault Tolerance configuration properties

PropertyDefault valueDescription



Number of threads used by the fault tolerance mechanisms. This does not include bulkhead thread pools.



Size of the thread pool used for scheduling timeouts.

9.3. Eclipse MicroProfile JWT reference

9.3.1. Eclipse MicroProfile Config JWT standard properties

The microprofile-jwt-smallrye subsystem supports the following Eclipse MicroProfile Config standard properties.

Table 9.4. Eclipse MicroProfile Config JWT standard properties




String representation of the public key encoded using one of the supported formats. Do not set if you have set mp.jwt.verify.publickey.location.



The location of the public key, may be a relative path or URL. Do not be set if you have set mp.jwt.verify.publickey.



The expected value of any iss claim of any JWT token being validated.

Example configuration:


9.4. Eclipse MicroProfile OpenAPI reference

9.4.1. Eclipse MicroProfile OpenAPI configuration properties

In addition to the standard Eclipse MicroProfile OpenAPI configuration properties, JBoss EAP supports the following additional Eclipse MicroProfile OpenAPI properties. These properties can be applied in both the global and the application scope.

Table 9.5. Eclipse MicroProfile OpenAPI properties in JBoss EAP

PropertyDefault valueDescription



Enables or disables registration of an OpenAPI endpoint.

When set to false, disables generation of OpenAPI documentation. You can set the value globally using the config subsystem, or for each application in a configuration file such as /META-INF/

You can parameterize this property to selectively enable or disable microprofile-openapi-smallrye in different environments, such as production or development.

You can use this property to control which application associated with a given virtual host should generate a MicroProfile OpenAPI model.



You can use this property for generating OpenAPI documentation for multiple applications associated with a virtual host.

Set a distinct mp.openapi.extensions.path on each application associated with the same virtual host.



Indicates whether auto-generated server records are absolute or relative to the location of the OpenAPI endpoint.

Server records are necessary to ensure, in the presence of a non-root context path, that consumers of an OpenAPI document can construct valid URLs to REST services relative to the host of the OpenAPI endpoint.

The value true indicates that the server records are relative to the location of the OpenAPI endpoint. The generated record contains the context path of the deployment.

When set to false, JBoss EAP XP generates server records including all the protocols, hosts, and ports at which the deployment is accessible.