The datasource pool maximum size

The datasource URL

The datasource password

The datasource username

Show SQL logs and format them nicely.

Setting it to true is obviously not recommended in production.

Origins allowed for CORS Comma separated list of valid URLs, e.g.: http://www.quarkus.io,http://localhost:3000 In case an entry of the list is surrounded by forward slashes, it is interpreted as a regular expression.

The HTTP port

Sets the default `from` attribute when not specified in the io.quarkus.mailer.Mail instance. It's the sender email address.

Sets the SMTP host name.

Enables the mock mode. When enabled, mails are not sent, but stored in an in-memory mailbox. The content of the emails is also printed on the console.

Disabled by default on PROD, enabled by default on DEV and TEST modes.

Sets the password to connect to the SMTP server.

The SMTP port. The default value depends on the configuration. The port 25 is used as default when #ssl is disabled. This port continues to be used primarily for SMTP relaying. SMTP relaying is the transmission of email from email server to email server. The port 587 is the default port when #ssl is enabled. It ensures that email is submitted securely. Note that the port 465 may be used by SMTP servers, however, IANA has reassigned a new service to this port, and it should no longer be used for SMTP communications.

Enables or disables the TLS/SSL.

Sets the username to connect to the SMTP server.

Certificate validation and hostname verification, which can be one of the following values from enum Verification. Default is required.

The base URL of the OpenID Connect (OIDC) server, for example, `https://host:port/auth`. OIDC discovery endpoint will be called by default by appending a '.well-known/openid-configuration' path to this URL. Note if you work with Keycloak OIDC server, make sure the base URL is in the following format: `https://host:port/realms/{realm}` where `{realm}` has to be replaced by the name of the Keycloak realm.

The client-id of the application. Each application has a client-id that is used to identify the application

Certificate validation and hostname verification, which can be one of the following values from enum Verification. Default is required.

Whether the banner will be displayed

What should happen if the application is started with a different build time configuration than it was compiled against. This may be useful to prevent misconfiguration.

If this is set to warn the application will warn at start up.

If this is set to fail the application will fail at start up.

Native tests leveraging@io.quarkus.test.junit.TestProfile are always run with quarkus.configuration.build-time-mismatch-at-runtime = fail.

The timeout before cancelling the acquisition of a new connection

The interval at which we validate idle connections in the background.

Set to 0 to disable background validation.

When enabled Agroal will be able to produce a warning when a connection is returned to the pool without the application having closed all open statements. This is unrelated with tracking of open connections. Disable for peak performance, but only when there's high confidence that no leaks are happening.

Collect and display extra troubleshooting info on leaked connections.

Allows connections to be flushed upon return to the pool. It's not enabled by default.

The interval at which we try to remove idle connections.

The datasource pool minimum size

Disable pooling to prevent reuse of Connections. Use this with when an external pool manages the life-cycle of Connections.

Trace calls with active Spans only

If set to true, Quarkus prints the wall-clock time each build step took to complete. This is useful as a first step in debugging slow startup times.

If Hibernate ORM should create the schemas automatically (for databases supporting them).

Whether we should stop on the first error when applying the schema.

Format the SQL logs if SQL log is enabled

The accept backlog, this is how many connections can be waiting to be accepted before connections start being rejected

The access log file base name, defaults to 'quarkus' which will give a log file name of 'quarkus.log'.

The log category to use if logging is being done via the standard log mechanism (i.e. if base-file-name is empty).

If access logging is enabled. By default this will log via the standard logging facility

The log file suffix

If logging should be done to a separate file.

The access log pattern.

If this is the string `common`, `combined` or `long` then this will use one of the specified named formats:

- common: `%h %l %u %t "%r" %s %b`
- combined: `%h %l %u %t "%r" %s %b "%{i,Referer}" "%{i,User-Agent}"`
- long: `%r\n%{ALL_REQUEST_HEADERS}`

Otherwise, consult the Quarkus documentation for the full list of variables that can be used.

If the log should be rotated daily

Whether the uploaded files should be removed after serving the request.

If true the uploaded files stored in quarkus.http.body-handler.uploads-directory will be removed after handling the request. Otherwise, the files will be left there forever.

Whether the files sent using multipart/form-data will be stored locally.

If true, they will be stored in quarkus.http.body-handler.uploads-directory and will be made available via io.vertx.ext.web.RoutingContext.fileUploads(). Otherwise, the files sent using multipart/form-data will not be stored locally, and io.vertx.ext.web.RoutingContext.fileUploads() will always return an empty collection. Note that even with this option being set to false, the multipart/form-data requests will be accepted.

Whether the form attributes should be added to the request parameters.

If true, the form attributes will be added to the request parameters; otherwise the form parameters will not be added to the request parameters

Whether the body buffer should pre-allocated based on the Content-Length header value.

If true the body buffer is pre-allocated according to the size read from the Content-Length header. Otherwise, the body buffer is pre-allocated to 1KB, and is resized dynamically

The directory where the files sent using multipart/form-data should be stored.

Either an absolute path or a path relative to the current directory of the application process.

Path to a unix domain socket

Enable listening to host:port

When set to true, the HTTP server automatically sends `100 CONTINUE` response when the request expects it (with the `Expect: 100-Continue` header).

Enable listening to host:port

If this is true (the default) then HTTP/2 will be enabled. Note that for browsers to be able to use it HTTPS must be enabled, and you must be running on JDK11 or above, as JDK8 does not support ALPN.

Http connection idle timeout

If insecure (i.e. http rather than https) requests are allowed. If this is enabled then http works as normal. redirect will still open the http port, but all requests will be redirected to the HTTPS port. disabled will prevent the HTTP port from opening at all.

The maximum size of a request body.

The max HTTP chunk size

The maximum length of a form attribute.

The maximum length of all headers.

The maximum length of the initial line (e.g. "GET / HTTP/1.0").

If this is true and proxy address forwarding is enabled then the standard Forwarded header will be used. In case the not standard X-Forwarded-For header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with quarkus.http.proxy.allow-x-forwarded has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-*` headers from the client.

Enable override the received request's host through a forwarded host header.

Enable prefix the received request's path with a forwarded prefix header.

Configure the forwarded host header to be used if override enabled.

Configure the forwarded prefix header to be used if prefixing enabled.

If this is true then the address, scheme etc. will be set from headers forwarded by the proxy server, such as X-Forwarded-For. This should only be set if you are behind a proxy that sets these headers.

Http connection read timeout for blocking IO. This is the maximum amount of time a thread will wait for data, before an IOException will be thrown and the connection closed.

If this is true then the request start time will be recorded to enable logging of total request time. This has a small performance penalty, so is disabled by default.

Enable socket reuse port (linux/macOs native transport only)

The HTTPS port

Sets the ordered list of enabled SSL/TLS protocols.

If not set, it defaults to "TLSv1.3, TLSv1.2". The following list of protocols are supported: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3. To only enable TLSv1.3, set the value to to "TLSv1.3".

Note that setting an empty list, and enabling SSL/TLS is invalid. You must at least have one protocol.

Enables Server Name Indication (SNI), an TLS extension allowing the server to use multiple certificates. The client indicate the server name during the TLS handshake, allowing the server to select the right certificate.

Set the cache entry timeout. The default is 30 seconds.

Set whether cache handling is enabled.

Set whether range requests (resumable downloads; media streaming) should be enabled.

Set whether hidden files should be served.

Set the index page when serving static resources.

Set value for max age in caching headers. The default is 24 hours.

Set the max cache size.

Enable tcp cork (linux native transport only)

Enable tcp fast open (linux native transport only)

Enable tcp quick ack (linux native transport only)

The HTTP port used to run tests

The HTTPS port used to run tests

Client id.

OAuth Grant Type.

Password. Required with a `password` grant type.

Realm.

Username. Required with a `password` grant type.

Determine whether to block the publisher (rather than drop the message) when the queue is full

The queue length to use before flushing writing

If console logging should be enabled

The log format. Note that this value will be ignored if an extension is present that takes control of console formatting (e.g. an XML or JSON-format extension).

The console log level.

If console logging should go to System#err instead of System#out.

Determine whether to block the publisher (rather than drop the message) when the queue is full

The queue length to use before flushing writing

If file logging should be enabled

The log format

The level of logs to be written into the file.

The name of the file in which logs will be written.

The maximum number of backups to keep.

The maximum file size of the log file after which a rotation is executed.

Indicates whether to rotate log files on server initialization.

You need to either set a max-file-size or configure a file-suffix for it to work.

The log level of the root category, which is used as the default log level for all categories.

JBoss Logging supports Apache style log levels:

* org.jboss.logmanager.Level#FATAL
* org.jboss.logmanager.Level#ERROR
* org.jboss.logmanager.Level#WARN
* org.jboss.logmanager.Level#INFO
* org.jboss.logmanager.Level#DEBUG
* org.jboss.logmanager.Level#TRACE

In addition, it also supports the standard JDK log levels.

Determine whether to block the publisher (rather than drop the message) when the queue is full

The queue length to use before flushing writing

Enables or disables blocking when attempting to reconnect a org.jboss.logmanager.handlers.SyslogHandler.Protocol#TCP TCP or org.jboss.logmanager.handlers.SyslogHandler.Protocol#SSL_TCP SSL TCP protocol

If syslog logging should be enabled

The IP address and port of the syslog server

Sets the facility used when calculating the priority of the message as defined by RFC-5424 and RFC-3164

The log message format

The log level specifying, which message levels will be logged by syslog logger

Sets the protocol used to connect to the syslog server

Set the SyslogType syslog type this handler should use to format the message sent

Set to true if the message should be truncated

Set to true if the message being sent should be prefixed with the size of the message

Sets if sending allows recipients errors. If set to true, the mail will be sent to the recipients that the server accepted, if any.

Disable ESMTP. The RFC-1869 states that clients should always attempt EHLO as first command to determine if ESMTP is supported, if this returns an error code, HELO is tried to use the regular SMTP command.

Enables DKIM signing.

Sets if connection pool is enabled. If the connection pooling is disabled, the max number of sockets is enforced nevertheless.

Set the keep alive timeout for the SMTP connection. This value determines how long a connection remains unused in the pool before being evicted and closed. A timeout of 0 means there is no timeout.

Sets the login mode for the connection. Either NONE, @{code DISABLED}, OPTIONAL, REQUIRED or XOAUTH2.

• DISABLED means no login will be attempted
• NONE means a login will be attempted if the server supports in and login credentials are set
• REQUIRED means that a login will be attempted if the server supports it and the send operation will fail otherwise
• XOAUTH2 means that a login will be attempted using Google Gmail Oauth2 tokens

Sets the max number of open connections to the mail server.

Whether the mail should always been sent as multipart even if they don't have attachments. When sets to true, the mail message will be encoded as multipart even for simple mails without attachments.

Enables or disables the pipelining capability if the SMTP server supports it.

Sets the connection pool cleaner period. Zero disables expiration checks and connections will remain in the pool until they are closed.

Sets the TLS security mode for the connection. Either DISABLED, OPTIONAL or REQUIRED.

Allow caching the token introspection data. Note enabling this property does not enable the cache itself but only permits to cache the token introspection for a given tenant. If the default token cache can be used then please see OidcConfig.TokenCache how to enable it.

Allow caching the user info data. Note enabling this property does not enable the cache itself but only permits to cache the user info data for a given tenant. If the default token cache can be used then please see OidcConfig.TokenCache how to enable it.

Allow caching the token introspection data. Note enabling this property does not enable the cache itself but only permits to cache the token introspection for a given tenant. If the default token cache can be used then please see OidcConfig.TokenCache how to enable it.

Allow caching the user info data. Note enabling this property does not enable the cache itself but only permits to cache the user info data for a given tenant. If the default token cache can be used then please see OidcConfig.TokenCache how to enable it.

If enabled the state, session and post logout cookies will have their 'secure' parameter set to 'true' when HTTP is used. It may be necessary when running behind an SSL terminating reverse proxy. The cookies will always be secure if HTTPS is used even if this property is set to false.

Cookie path parameter value which, if set, will be used to set a path parameter for the session, state and post logout cookies. The `cookie-path-header` property, if set, will be checked first.

SameSite attribute for the session cookie.

If this property is set to 'true' then a normal 302 redirect response will be returned if the request was initiated via JavaScript API such as XMLHttpRequest or Fetch and the current user needs to be (re)authenticated which may not be desirable for Single Page Applications since it automatically following the redirect may not work given that OIDC authorization endpoints typically do not support CORS. If this property is set to `false` then a status code of '499' will be returned to allow the client to handle the redirect manually

Remove the query parameters such as 'code' and 'state' set by the OIDC server on the redirect URI after the user has authenticated by redirecting a user to the same URI but without the query parameters.

If this property is set to 'true' then the original request URI which was used before the authentication will be restored after the user has been redirected back to the application. Note if `redirectPath` property is not set, the original request URI will be restored even if this property is disabled.

Session age extension in minutes. The user session age property is set to the value of the ID token life-span by default and the user will be redirected to the OIDC provider to re-authenticate once the session has expired. If this property is set to a non-zero value then the expired ID token can be refreshed before the session has expired. This property will be ignored if the `token.refresh-expired` property has not been enabled.

Both ID and access tokens are fetched from the OIDC provider as part of the authorization code flow. ID token is always verified on every user request as the primary token which is used to represent the principal and extract the roles. Access token is not verified by default since it is meant to be propagated to the downstream services. The verification of the access token should be enabled if it is injected as a JWT token. Access tokens obtained as part of the code flow will always be verified if `quarkus.oidc.roles.source` property is set to `accesstoken` which means the authorization decision will be based on the roles extracted from the access token. Bearer access tokens are always verified.

Allow inlining UserInfo in IdToken instead of caching it in the token cache. This property is only checked when an internal IdToken is generated when Oauth2 providers do not return IdToken. Inlining UserInfo in the generated IdToken allows to store it in the session cookie and avoids introducing a cached state.

The number of times an attempt to re-establish an already available connection will be repeated for. Note this property is different to the `connection-delay` property which is only effective during the initial OIDC connection creation. This property is used to try to recover the existing connection which may have been temporarily lost. For example, if a request to the OIDC token endpoint fails due to a connection exception then the request will be retried for a number of times configured by this property.

The amount of time after which the current OIDC connection request will time out.

The private key password

A parameter to specify the password of the key store file. If not given, the default ("password") is used.

JWT life-span in seconds. It will be added to the time it was issued at to calculate the expiration time.

Include OpenId Connect Client ID configured with 'quarkus.oidc.client-id'

Name of the post logout URI parameter which will be added as a query parameter to the logout redirect URI.

The port number of the Proxy. Default value is 80.

If this tenant configuration is enabled.

A parameter to specify the password of the key store file. If not given, the default ("password") is used.

Default TokenStateManager keeps all tokens (ID, access and refresh) returned in the authorization code grant response in a single session cookie by default. Enable this property to minimize a session cookie size

Default TokenStateManager strategy.

Allow the remote introspection of JWT tokens when no matching JWK key is available. Note this property is set to 'true' by default for backward-compatibility reasons and will be set to `false` instead in one of the next releases. Also note this property will be ignored if JWK endpoint URI is not available and introspecting the tokens is the only verification option.

Allow the remote introspection of the opaque tokens. Set this property to 'false' if only JWT tokens are expected.

Forced JWK set refresh interval in minutes.

Refresh expired authorization code flow ID or access tokens. If this property is enabled then a refresh token request will be performed if the authorization code ID or access token has expired and, if successful, the local session will be updated with the new set of tokens. Otherwise, the local session will be invalidated and the user redirected to the OpenID Provider to re-authenticate. In this case the user may not be challenged again if the OIDC provider session is still active. For this option be effective the `authentication.session-age-extension` property should also be set to a non-zero value since the refresh token is currently kept in the user session. This option is valid only when the application is of type ApplicationType#WEB_APP}.

Require that JWT tokens are only introspected remotely.

Indirectly verify that the opaque (binary) access token is valid by using it to request UserInfo. Opaque access token is considered valid if the provider accepted this token and returned a valid UserInfo. You should only enable this option if the opaque access tokens have to be accepted but OpenId Connect provider does not have a token introspection endpoint. This property will have no effect when JWT tokens have to be verified.

If enabled the state, session and post logout cookies will have their 'secure' parameter set to 'true' when HTTP is used. It may be necessary when running behind an SSL terminating reverse proxy. The cookies will always be secure if HTTPS is used even if this property is set to false.

Cookie path parameter value which, if set, will be used to set a path parameter for the session, state and post logout cookies. The `cookie-path-header` property, if set, will be checked first.

SameSite attribute for the session cookie.

If this property is set to 'true' then a normal 302 redirect response will be returned if the request was initiated via JavaScript API such as XMLHttpRequest or Fetch and the current user needs to be (re)authenticated which may not be desirable for Single Page Applications since it automatically following the redirect may not work given that OIDC authorization endpoints typically do not support CORS. If this property is set to `false` then a status code of '499' will be returned to allow the client to handle the redirect manually

Remove the query parameters such as 'code' and 'state' set by the OIDC server on the redirect URI after the user has authenticated by redirecting a user to the same URI but without the query parameters.

If this property is set to 'true' then the original request URI which was used before the authentication will be restored after the user has been redirected back to the application. Note if `redirectPath` property is not set, the original request URI will be restored even if this property is disabled.

Session age extension in minutes. The user session age property is set to the value of the ID token life-span by default and the user will be redirected to the OIDC provider to re-authenticate once the session has expired. If this property is set to a non-zero value then the expired ID token can be refreshed before the session has expired. This property will be ignored if the `token.refresh-expired` property has not been enabled.

Both ID and access tokens are fetched from the OIDC provider as part of the authorization code flow. ID token is always verified on every user request as the primary token which is used to represent the principal and extract the roles. Access token is not verified by default since it is meant to be propagated to the downstream services. The verification of the access token should be enabled if it is injected as a JWT token. Access tokens obtained as part of the code flow will always be verified if `quarkus.oidc.roles.source` property is set to `accesstoken` which means the authorization decision will be based on the roles extracted from the access token. Bearer access tokens are always verified.

Allow inlining UserInfo in IdToken instead of caching it in the token cache. This property is only checked when an internal IdToken is generated when Oauth2 providers do not return IdToken. Inlining UserInfo in the generated IdToken allows to store it in the session cookie and avoids introducing a cached state.

The number of times an attempt to re-establish an already available connection will be repeated for. Note this property is different to the `connection-delay` property which is only effective during the initial OIDC connection creation. This property is used to try to recover the existing connection which may have been temporarily lost. For example, if a request to the OIDC token endpoint fails due to a connection exception then the request will be retried for a number of times configured by this property.

The amount of time after which the current OIDC connection request will time out.

The private key password

A parameter to specify the password of the key store file. If not given, the default ("password") is used.

JWT life-span in seconds. It will be added to the time it was issued at to calculate the expiration time.

Include OpenId Connect Client ID configured with 'quarkus.oidc.client-id'

Name of the post logout URI parameter which will be added as a query parameter to the logout redirect URI.

The port number of the Proxy. Default value is 80.

If this tenant configuration is enabled.

A parameter to specify the password of the key store file. If not given, the default ("password") is used.

Maximum number of cache entries. Set it to a positive value if the cache has to be enabled.

Maximum amount of time a given cache entry is valid for.

Default TokenStateManager keeps all tokens (ID, access and refresh) returned in the authorization code grant response in a single session cookie by default. Enable this property to minimize a session cookie size

Default TokenStateManager strategy.

Allow the remote introspection of JWT tokens when no matching JWK key is available. Note this property is set to 'true' by default for backward-compatibility reasons and will be set to `false` instead in one of the next releases. Also note this property will be ignored if JWK endpoint URI is not available and introspecting the tokens is the only verification option.

Allow the remote introspection of the opaque tokens. Set this property to 'false' if only JWT tokens are expected.

Forced JWK set refresh interval in minutes.

Refresh expired authorization code flow ID or access tokens. If this property is enabled then a refresh token request will be performed if the authorization code ID or access token has expired and, if successful, the local session will be updated with the new set of tokens. Otherwise, the local session will be invalidated and the user redirected to the OpenID Provider to re-authenticate. In this case the user may not be challenged again if the OIDC provider session is still active. For this option be effective the `authentication.session-age-extension` property should also be set to a non-zero value since the refresh token is currently kept in the user session. This option is valid only when the application is of type ApplicationType#WEB_APP}.

Require that JWT tokens are only introspected remotely.

Indirectly verify that the opaque (binary) access token is valid by using it to request UserInfo. Opaque access token is considered valid if the provider accepted this token and returned a valid UserInfo. You should only enable this option if the opaque access tokens have to be accepted but OpenId Connect provider does not have a token introspection endpoint. This property will have no effect when JWT tokens have to be verified.

Specify whether the parser should remove standalone lines from the output. A standalone line is a line that contains at least one section tag, parameter declaration, or comment but no expression and no non-whitespace character.

If set to true then any expression that is evaluated to a Results.NotFound value will always result in a TemplateException and the rendering is aborted.

Note that the quarkus.qute.property-not-found-strategy config property is completely ignored if strict rendering is enabled.

The global rendering timeout in milliseconds. It is used if no timeout template instance attribute is set.

If set to true then the timeout should also be used for asynchronous rendering methods, such as TemplateInstance#createUni() and TemplateInstance#renderAsync().

A timeout in milliseconds that REST clients should wait to connect to the remote endpoint. Can be overwritten by client-specific settings.

If true, the REST clients will not provide additional contextual information (like REST client class and method names) when exception occurs during a client invocation. This property is applicable to reactive REST clients only.

By default, REST Client Reactive uses text/plain content type for String values and application/json for everything else. MicroProfile Rest Client spec requires the implementations to always default to application/json. This build item disables the "smart" behavior of RESTEasy Reactive to comply to the spec. This property is applicable to reactive REST clients only.

If set to false disables the keep alive completely. Can be overwritten by client-specific settings.

How many characters of the body should be logged. Message body can be large and can easily pollute the logs. By default, set to 100. This property is applicable to reactive REST clients only.

A timeout in milliseconds that REST clients should wait for a response from the remote endpoint. Can be overwritten by client-specific settings.

Default charset.

Note that the default value is UTF-8 which is different from RESTEasy's default value US-ASCII.

The default content-type.

If schedulers are enabled.

Scheduled task will be flagged as overdue if next execution time is exceeded by this period.

Enable the openapi endpoint. By default it's enabled.

If Swagger UI is included, it should be enabled/disabled. By default, Swagger UI is enabled if it is included (see always-include).

The core thread pool size. This number of threads will always be kept alive.

The executor growth resistance. A resistance factor applied after the core pool is full; values applied here will cause that fraction of submissions to create new threads when no idle thread is available. A value of 0.0f implies that threads beyond the core size should be created as aggressively as threads within it; a value of 1.0f implies that threads beyond the core size should never be created.

The amount of time a thread will stay alive with no work.

Prefill core thread pool. The core thread pool will be initialised with the core number of threads at startup

The frequency at which the status of the thread pool should be checked during shutdown. Information about waiting tasks and threads will be checked and possibly logged at this interval. Setting this key to an empty value disables the shutdown check interval.

The amount of time to wait for thread pool shutdown before tasks should be interrupted. If this value is greater than or equal to the value for #shutdownTimeout, then tasks will not be interrupted before the shutdown timeout occurs.

The shutdown timeout. If all pending work has not been completed by this time then additional threads will be spawned to attempt to finish any pending tasks, and the shutdown process will continue

The default transaction timeout

Start the recovery service on startup.

The list of expiry scanners

The node name used by the transaction manager

The directory name of location of the transaction logs. If the value is not absolute then the directory is relative to the user.dir system property.

The list of recovery modules

The list of orphan filters

Enables or disables the Vert.x cache.

Enables or disabled the Vert.x classpath resource resolver.

Enables or disables the clustering.

The host name.

The ping interval.

The ping reply interval.

The client authentication.

The connect timeout.

The number of reconnection attempts.

The reconnection interval in milliseconds.

Whether to reuse the address.

Whether to reuse the port.

Enables or Disabled SSL.

Whether to keep the TCP connection opened (keep-alive).

Configure the TCP no delay.

Enables or disables the trust all parameter.

The executor growth resistance. A resistance factor applied after the core pool is full; values applied here will cause that fraction of submissions to create new threads when no idle thread is available. A value of 0.0f implies that threads beyond the core size should be created as aggressively as threads within it; a value of 1.0f implies that threads beyond the core size should never be created.

The size of the internal thread pool (used for the file system).

The amount of time a thread will stay alive with no work.

The maximum amount of time the event loop can be blocked.

The maximum amount of time the worker thread can be blocked.

Enable or disable native transport

Prefill thread pool when creating a new Executor. When {
@see io.vertx.core.spi.ExecutorServiceFactory.createExecutor} is called, initialise with the number of defined threads at startup

The maximum amount of time in seconds that a successfully resolved address will be cached.

If not set explicitly, resolved addresses may be cached forever.

The minimum amount of time in seconds that a successfully resolved address will be cached.

The amount of time in seconds that an unsuccessful attempt to resolve an address will be cached.

The maximum number of queries to be sent during a resolution.

The duration after which a DNS query is considered to be failed.

Enables the async DNS resolver.

The amount of time before a warning is displayed if the event loop is blocked.

The size of the worker thread pool.

The name of the application. If not set, defaults to the name of the project (except for tests where it is not set at all).

The header to use for UI Screen (Swagger UI, GraphQL UI etc).

The version of the application. If not set, defaults to the version of the project (except for tests where it is not set at all).

The kind of database we will connect to (e.g. h2, postgresql...).

Whether this particular data source should be excluded from the health check if the general health check for data sources is enabled.

By default, the health check includes all configured data sources (if it is enabled).

Whether or not an health check is published in case the smallrye-health extension is present.

This is a global setting and is not specific to a datasource.

Enable JDBC tracing. Disabled by default.

Whether we want to use regular JDBC transactions, XA, or disable all transactional capabilities.

When enabling XA you will need a driver implementing javax.sql.XADataSource.

Whether or not datasource metrics are published in case a metrics extension is present.

This is a global setting and is not specific to a datasource.

NOTE: This is different from the "jdbc.enable-metrics" property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.

Default locale that can be consumed by the extensions.

The locale must be specified in the IETF BCP 47 format e.g. en-US or fr-FR.

For instance, the Hibernate Validator extension makes use of it.

Native-image build uses this property to derive user.language and user.country for the application's runtime.

Enable the fail fast mode. When fail fast is enabled the validation will stop on the first constraint violation detected.

Define whether more than one constraint on a return value may be marked for cascading validation are allowed. The default value is false, i.e. do not allow.

See Section 4.5.5 of the JSR 380 specification, specifically

"One must not mark a method return value for cascaded validation more than once in a line of a class hierarchy.
In other words, overriding methods on sub types (be it sub classes/interfaces or interface implementations)
cannot mark the return value for cascaded validation if the return value has already been marked on the
overridden method of the super type or interface."

Define whether overriding methods that override constraints should throw a ConstraintDefinitionException. The default value is false, i.e. do not allow.

See Section 4.5.5 of the JSR 380 specification, specifically

"In sub types (be it sub classes/interfaces or interface implementations), no parameter constraints may
be declared on overridden or implemented methods, nor may parameters be marked for cascaded validation.
This would pose a strengthening of preconditions to be fulfilled by the caller."

Define whether parallel methods that define constraints should throw a ConstraintDefinitionException. The default value is false, i.e. do not allow.

See Section 4.5.5 of the JSR 380 specification, specifically

"If a sub type overrides/implements a method originally defined in several parallel types of the hierarchy
(e.g. two interfaces not extending each other, or a class and an interface not implemented by said class),
no parameter constraints may be declared for that method at all nor parameters be marked for cascaded validation.
This again is to avoid an unexpected strengthening of preconditions to be fulfilled by the caller."

The cookie that is used to store the persistent session

The cookie path for the session and location cookies.

SameSite attribute for the session and location cookies.

If form authentication is enabled.

The error page. Redirect to error page can be disabled by setting `quarkus.http.auth.form.error-page=`.

Set the HttpOnly attribute to prevent access to the cookie via JavaScript.

The landing page to redirect to if there is no saved page to redirect back to. Redirect to landing page can be disabled by setting `quarkus.http.auth.form.landing-page=`.

Option to control the name of the cookie used to redirect the user back to where he wants to get access to.

The login page. Redirect to login page can be disabled by setting `quarkus.http.auth.form.login-page=`.

How old a cookie can get before it will be replaced with a new cookie with an updated timeout, also referred to as "renewal-timeout". Note that smaller values will result in slightly more server load (as new encrypted cookies will be generated more often), however larger values affect the inactivity timeout as the timeout is set when a cookie is generated. For example if this is set to 10 minutes, and the inactivity timeout is 30m, if a users last request is when the cookie is 9m old then the actual timeout will happen 21m after the last request, as the timeout is only refreshed when a new cookie is generated. In other words no timeout is tracked on the server side; the timestamp is encoded and encrypted in the cookie itself, and it is decrypted and parsed with each request.

The password field name.

The post location.

Option to disable redirect to landingPage if there is no saved page to redirect back to. Form Auth POST is followed by redirect to landingPage by default.
@deprecated redirect to landingPage can be disabled by removing default landing page (via `quarkus.http.auth.form.landing-page=`). Quarkus will ignore this configuration property if there is no landing page.

The inactivity (idle) timeout When inactivity timeout is reached, cookie is not renewed and a new login is enforced.

The username field name.

If this is true and credentials are present then a user will always be authenticated before the request progresses. If this is false then an attempt will only be made to authenticate the user if a permission check is performed or the current user is required for some other reason.

List of media types for which the compression should be enabled automatically, unless declared explicitly via Compressed or Uncompressed.

If responses should be compressed. Note that this will attempt to compress all responses, to avoid compressing already compressed content (such as images) you need to set the following header: Content-Encoding: identity Which will tell vert.x not to compress the response.

When enabled, vert.x will decompress the request's body if it's compressed. Note that the compression format (e.g., gzip) must be specified in the Content-Encoding header in the request.

A common root path for non-application endpoints. Various extension-provided endpoints such as metrics, health,
and openapi are deployed under this path by default.

* Relative path (Default, `q`) ->
Non-application endpoints will be served from
`${quarkus.http.root-path}/${quarkus.http.non-application-root-path}`.
* Absolute path (`/q`) ->
Non-application endpoints will be served from the specified path.
* `${quarkus.http.root-path}` -> Setting this path to the same value as HTTP root path disables
this root path. All extension-provided endpoints will be served from `${quarkus.http.root-path}`.

The HTTP root path. All web content will be served relative to this root path.

Configures the engine to require/request client authentication. NONE, REQUEST, REQUIRED

The REST Assured client timeout for testing.

If this is true then only a virtual channel will be set up for vertx web. We have this switch for testing purposes.

If enabled, Jackson will ignore case during Enum deserialization.

If enabled, Jackson will fail when no accessors are found for a type. This is enabled by default to match the default Jackson behavior.

If enabled, Jackson will fail when encountering unknown properties.

You can still override it locally with @JsonIgnoreProperties(ignoreUnknown = false).

If set, Jackson will default to using the specified timezone when formatting dates. Some examples values are "Asia/Jakarta" and "GMT+3". If not set, Jackson will use its own default.

If enabled, Jackson will serialize dates as numeric value(s). When disabled, they are serialized in ISO 8601 format.

If enabled, Jackson will serialize durations as numeric value(s). When disabled, they are serialized in ISO 8601 format. This is enabled by default to match the default Jackson behavior.

Adapters will make separate HTTP invocations to the Keycloak server to turn an access code into an access token. This config option defines how many connections to the Keycloak server should be pooled

Specifies how policies are enforced.

Specifies how scopes should be mapped to HTTP methods. If set to true, the policy enforcer will use the HTTP method from the current request to check whether access should be granted

Specifies how the adapter should fetch the server for resources associated with paths in your application. If true, the policy enforcer is going to fetch resources on-demand accordingly with the path being requested

Defines the time in milliseconds when the entry should be expired

Defines the limit of entries that should be kept in the cache

The amount of time to wait for a remote dev connect or reconnect

Whether Quarkus should enable its ability to not do a full restart when changes to classes are compatible with JVM instrumentation. If this is set to true, Quarkus will perform class redefinition when possible.

The amount of time to wait between attempts when connecting to the server side of remote dev

The maximum number of attempts when connecting to the server side of remote dev

The set of supported locales that can be consumed by the extensions.

The locales must be specified in the IETF BCP 47 format e.g. en-US or fr-FR.

For instance, the Hibernate Validator extension makes use of it.

Native-image build uses it to define additional locales that are supposed to be available at runtime.

Whether logging metrics are published in case a metrics extension is present.

The default minimum log level.

Caches data from attachment's Stream to a temporary file. It tries to delete it after sending email.

The default charset of the templates files.

The list of content types for which the ', ", <, > and & characters are escaped if a template variant is set.

The prefix is used to access the iteration metadata inside a loop section.

A valid prefix consists of alphanumeric characters and underscores. Three special constants can be used:

• - the alias of an iterated element suffixed with an underscore is used, e.g. item_hasNext and it_count
• - the alias of an iterated element suffixed with a question mark is used, e.g. item?hasNext and it?count
• - no prefix is used, e.g. hasNext and count

The list of suffixes used when attempting to locate a template file.

By default, `engine.getTemplate("foo")` would result in several lookups: `foo`, `foo.html`, `foo.txt`, etc.

This regular expression is used to exclude template files from the templates directory. Excluded templates are neither parsed nor validated during build and are not available at runtime.

The matched input is the file path relative from the templates directory and the / is used as a path separator.

By default, the hidden files are excluded. The name of a hidden file starts with a dot.

The syntax used in CRON expressions.
@see Scheduled#cron()

Scheduled task metrics will be enabled if a metrics extension is present and this value is true.

Tracing will be enabled if the OpenTelemetry extension is present and this value is true.

If set to true, access to all methods of beans that have any security annotations on other members will be denied by default. E.g. if enabled, in the following bean, methodB will be denied.

  {@literal @}ApplicationScoped
  public class A {
     {@literal @}RolesAllowed("admin")
     public void methodA() {
         ...
     }
     public void methodB() {
         ...
     }
  }

if set to true, access to all JAX-RS resources will be denied by default

Enable trusting all certificates. Disable by default.

If set to true @Inject is automatically added to all non-static non-final fields that are annotated with one of the annotations defined by AutoInjectAnnotationBuildItem.

If set to true then javax.enterprise.inject.Produces is automatically added to all non-void methods that are annotated with a scope annotation, a stereotype or a qualifier, and are not annotated with Inject or Produces, and no parameter is annotated with Disposes, Observes or ObservesAsync.

If set to true and SmallRye Context Propagation extension is present then enable the context propagation for CDI contexts.

If set to true then the container attempts to detect "unused removed beans" false positives during programmatic lookup at runtime. You can disable this feature to conserve some memory when running your application in production.
@see ArcConfig#removeUnusedBeans

If set to true then the container attempts to detect wrong usages of annotations and eventually fails the build to prevent unexpected behavior of a Quarkus application.

A typical example is @javax.ejb.Singleton which is often confused with @javax.inject.Singleton. As a result a component annotated with @javax.ejb.Singleton would be completely ignored. Another example is an inner class annotated with a scope annotation - this component would be again completely ignored.

If set to true then the container monitors business method invocations and fired events during the development mode.

The list of types that should be excluded from discovery.

An element value can be:

• a fully qualified class name, i.e. org.acme.Foo
• a simple class name as defined by Class#getSimpleName(), i.e. Foo
• a package name with suffix .*, i.e. org.acme.*, matches a package
• a package name with suffix .**, i.e. org.acme.**, matches a package that starts with the value

If set to true, the build fails if a private method that is neither an observer nor a producer, is annotated with an interceptor binding. An example of this is the use of Transactional on a private method of a bean. If set to false, Quarkus simply logs a warning that the annotation will be ignored.

The list of packages that will not be checked for split package issues.

A package string representation can be:

• a full name of the package, i.e. org.acme.foo
• a package name with suffix .*, i.e. org.acme.*, which matches a package that starts with provided value
Environment variable: QUARKUS_ARC_IGNORED_SPLIT_PACKAGES

• If set to all (or true) the container will attempt to remove all unused beans.
• If set to none (or false) no beans will ever be removed even if they are unused (according to the criteria set out below)
• If set to fwk, then all unused beans will be removed, except the unused beans whose classes are declared in the application code

An unused bean:

• is not a built-in bean or interceptor,
• is not eligible for injection to any injection point,
• is not excluded by any extension,
• does not have a name,
• does not declare an observer,
• does not declare any producer which is eligible for injection to any injection point,
• is not directly eligible for injection into any javax.enterprise.inject.Instance injection point

The list of selected alternatives for an application.

An element value can be:

• a fully qualified class name, i.e. org.acme.Foo
• a simple class name as defined by Class#getSimpleName(), i.e. Foo
• a package name with suffix .*, i.e. org.acme.*, matches a package
• a package name with suffix .**, i.e. org.acme.**, matches a package that starts with the value

If set to true then disable StartupEvent and ShutdownEvent observers declared on application bean classes during the tests.

If set to true, the bytecode of unproxyable beans will be transformed. This ensures that a proxy/subclass can be created properly. If the value is set to false, then an exception is thrown at build time indicating that a subclass/proxy could not be created. Quarkus performs the following transformations when this setting is enabled:

• Remove 'final' modifier from classes and methods when a proxy is required.
• Create a no-args constructor if needed.
• Makes private no-args constructors package-private if necessary.
  Environment variable: QUARKUS_ARC_TRANSFORM_UNPROXYABLE_CLASSES

List of types that should be considered unremovable regardless of whether they are directly used or not. This is a configuration option equivalent to using io.quarkus.arc.Unremovable annotation.

An element value can be:

• a fully qualified class name, i.e. org.acme.Foo
• a simple class name as defined by Class#getSimpleName(), i.e. Foo
• a package name with suffix .*, i.e. org.acme.*, matches a package
• a package name with suffix .**, i.e. org.acme.**, matches a package that starts with the value

The arguments passed to the command line.

We don't make it a list as the args are separated by a space, not a comma.

The path of the banner (path relative to root of classpath) which could be provided by user

If set to true, the workspace initialization will be based on the effective POMs (i.e. properly interpolated, including support for profiles) instead of the raw ones.

Whether to throw an error, warn or silently ignore misaligned platform BOM imports

If set to true, workspace discovery will be enabled for all launch modes. Usually, workspace discovery is enabled by default only for dev and test modes.

Artifacts that are loaded in a parent first manner. This can be used to work around issues where a given class needs to be loaded by the system ClassLoader. Note that if you make a library parent first all its dependencies should generally also be parent first.

Artifacts should be configured as a comma separated list of artifact ids, with the group, artifact-id and optional classifier separated by a colon.

WARNING: This config property can only be set in application.properties

Artifacts that are loaded in the runtime ClassLoader in dev mode, so they will be dropped and recreated on change.

This is an advanced option, it should only be used if you have a problem with libraries holding stale state between reloads. Note that if you use this any library that depends on the listed libraries will also need to be reloadable.

This setting has no impact on production builds.

Artifacts should be configured as a comma separated list of artifact ids, with the group, artifact-id and optional classifier separated by a colon.

WARNING: This config property can only be set in application.properties

Artifacts that will never be loaded by the class loader, and will not be packed into the final application. This allows you to explicitly remove artifacts from your application even though they may be present on the class path.

Additional config locations to be loaded with the Config. The configuration support multiple locations separated by a comma and each must represent a valid java.net.URI.

Accepts a single configuration profile name. If a configuration property cannot be found in the current active profile, the config performs the same lookup in the profile set by this configuration.

Set this to true to read configuration from system properties and environment variables only. This only applies to runtime.

Disable the testing status/prompt message at the bottom of the console and log these messages to STDOUT instead.

Use this option if your terminal does not support ANSI escape sequences.

If color should be enabled or disabled. If this is not present then an attempt will be made to guess if the terminal supports color

Disables the ability to enter input on the console.

If test results and status should be displayed in the console.

If this is false results can still be viewed in the dev console.

The credentials provider name

The credentials provider bean name.

It is the @Named value of the credentials provider bean. It is used to discriminate if multiple CredentialsProvider beans are available.

For Vault it is: vault-credentials-provider. Not necessary if there is only one credentials provider available.

The container start command to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect.

The name of the database to use if this Dev Service supports overriding it.

If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode.

The container image name to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect.

Path to a SQL script that will be loaded from the classpath and applied to the Dev Service database If the provider is not container based (e.g. a H2 or Derby Database) then this has no effect.

The password to use if this Dev Service supports overriding it.

Optional fixed port the dev service will listen to.

If not defined, the port will be chosen randomly.

The username to use if this Dev Service supports overriding it.

The datasource driver class name

Enable datasource metrics collection. If unspecified, collecting metrics will be enabled by default if a metrics extension is active.

Perform foreground validation on connections that have been idle for longer than the specified interval.

The initial size of the pool. Usually you will want to set the initial size to match at least the minimal size, but this is not enforced so to allow for architectures which prefer a lazy initialization of the connections on boot, while being able to sustain a minimal pool size after boot.

The interval at which we check for connection leaks.

The max lifetime of a connection.

Query executed when first using a connection.

Enable JDBC tracing.

Ignore specific queries from being traced

The transaction isolation level.

Require an active transaction when acquiring a connection. Recommended for production. WARNING: Some extensions acquire connections without holding a transaction for things like schema updates and schema validation. Setting this setting to STRICT may lead to failures in those cases.

Query executed to validate a connection.

If set to a directory, all generated classes will be written into that directory

If set to a directory, ZIG files for generated code will be written into that directory.

A ZIG file is a textual representation of the generated code that is referenced in the stacktraces.

If set to true, writes a list of all reflective classes to META-INF

If set to a directory, all transformed classes (e.g. Panache entities) will be written into that directory

Enable CORS filter.

The number of history log entries to remember.

Global flag that can be used to disable all Dev Services. If this is set to false then Dev Services will not be used.

The timeout for starting a container

Whether this persistence unit should be active at runtime.

If the persistence unit is not active, it won't start with the application,
and accessing the corresponding EntityManagerFactory/EntityManager or SessionFactory/Session
will not be possible.

Note that if Hibernate ORM is disabled (i.e. `quarkus.hibernate-orm.enabled` is set to `false`),
all persistence units are deactivated, and setting this property to `true` will fail.

The size of the batches used when loading entities and collections.

`-1` means batch loading is disabled.

@deprecated #fetch should be used to configure fetching properties.

The charset of the database.

Used for DDL generation and also for the SQL import scripts.

The default catalog to use for the database objects.

The default schema to use for the database objects.

Whether Hibernate should quote all identifiers.

The storage engine to use when the dialect supports multiple storage engines.

E.g. `MyISAM` or `InnoDB` for MySQL.

Existing applications rely (implicitly or explicitly) on Hibernate ignoring any DiscriminatorColumn declarations on joined inheritance hierarchies. This setting allows these applications to maintain the legacy behavior of DiscriminatorColumn annotations being ignored when paired with joined inheritance.

Whether Hibernate ORM is enabled *during the build*.

If Hibernate ORM is disabled during the build, all processing related to Hibernate ORM will be skipped,
but it will not be possible to activate Hibernate ORM at runtime:
`quarkus.hibernate-orm.active` will default to `false` and setting it to `true` will lead to an error.

The size of the batches used when loading entities and collections.

`-1` means batch loading is disabled.

The maximum depth of outer join fetch tree for single-ended associations (one-to-one, many-to-one).

A `0` disables default outer join fetching.

Pluggable strategy for applying implicit naming rules when an explicit name is not given. Class name of the Hibernate ImplicitNamingStrategy implementation

The number of updates (inserts, updates and deletes) that are sent by the JDBC driver at one time for execution.

How many rows are fetched at a time by the JDBC driver.

The time zone pushed to the JDBC driver.

Whether session metrics should be appended into the server log for each Hibernate session. This only has effect if statistics are enabled (`quarkus.hibernate-orm.statistics`). The default is false (which means both `statistics` and `log-session-metrics` need to be enabled for the session metrics to appear in the log).

Logs SQL bind parameter.

Setting it to true is obviously not recommended in production.

Logs SQL bind parameters.

Setting it to true is obviously not recommended in production.

Whether JDBC warnings should be collected and logged.

If set, Hibernate will log queries that took more than specified number of milliseconds to execute.

XML files to configure the entity mapping, e.g. META-INF/my-orm.xml.

Defaults to `META-INF/orm.xml` if it exists. Pass `no-file` to force Hibernate ORM to ignore `META-INF/orm.xml`.

The maximum depth of outer join fetch tree for single-ended associations (one-to-one, many-to-one).

A `0` disables default outer join fetching.

@deprecated #fetch should be used to configure fetching properties.

Class name of a custom
https://docs.jboss.org/hibernate/stable/orm/javadocs/org/hibernate/boot/spi/MetadataBuilderContributor.html[`org.hibernate.boot.spi.MetadataBuilderContributor`]
implementation.

[NOTE]
====
Not all customization options exposed by
https://docs.jboss.org/hibernate/stable/orm/javadocs/org/hibernate/boot/MetadataBuilder.html[`org.hibernate.boot.MetadataBuilder`]
will work correctly. Stay clear of options related to classpath scanning in particular.

This setting is exposed mainly to allow registration of types, converters and SQL functions.
====

Whether metrics are published if a metrics extension is enabled.

Defines the method for multi-tenancy (DATABASE, NONE, SCHEMA). The complete list of allowed values is available in the
https://javadoc.io/doc/org.hibernate/hibernate-core/5.6.10.Final/org/hibernate/MultiTenancyStrategy.html[Hibernate ORM
JavaDoc].
The type DISCRIMINATOR is currently not supported. The default value is NONE (no multi-tenancy).

Defines the name of the datasource to use in case of SCHEMA approach. The datasource of the persistence unit will be used if not set.

Pluggable strategy contract for applying physical naming rules for database object names. Class name of the Hibernate PhysicalNamingStrategy implementation

Default precedence of null values in `ORDER BY` clauses.

Valid values are: `none`, `first`, `last`.

Enables IN clause parameter padding which improves statement caching.

The maximum size of the query plan cache. see #{@value QueryPlanCache#DEFAULT_QUERY_PLAN_MAX_COUNT}

Filename or URL where the database create DDL file should be generated.

Filename or URL where the database drop DDL file should be generated.

The default in Quarkus is for 2nd level caching to be enabled, and a good implementation is already integrated for you.

Just cherry-pick which entities should be using the cache.

Set this to false to disable all 2nd level caches.

Path to a file containing the SQL statements to execute when Hibernate ORM starts.

The file is retrieved from the classpath resources,
so it must be located in the resources directory (e.g. `src/main/resources`).

The default value for this setting differs depending on the Quarkus launch mode:

* In dev and test modes, it defaults to `import.sql`.
Simply add an `import.sql` file in the root of your resources directory
and it will be picked up without having to set this property.
Pass `no-file` to force Hibernate ORM to ignore the SQL import file.
* In production mode, it defaults to `no-file`.
It means Hibernate ORM won't try to execute any SQL import file by default.
Pass an explicit value to force Hibernate ORM to execute the SQL import file.

If you need different SQL statements between dev mode, test (`@QuarkusTest`) and in production, use Quarkus
https://quarkus.io/guides/config#configuration-profiles[configuration profiles facility].

[source,property]
.application.properties
----
%dev.quarkus.hibernate-orm.sql-load-script = import-dev.sql
%test.quarkus.hibernate-orm.sql-load-script = import-test.sql
%prod.quarkus.hibernate-orm.sql-load-script = no-file
----

[NOTE]
====
Quarkus supports `.sql` file with SQL statements or comments spread over multiple lines.
Each SQL statement must be terminated by a semicolon.
====

Whether statistics collection is enabled. If 'metrics.enabled' is true, then the default here is considered true, otherwise the default is false.

If hibernate is not auto generating the schema, and Quarkus is running in development mode then Quarkus will attempt to validate the database after startup and print a log message if there are any problems.

Configure the Expression Language feature level for constraints, allowing the selection of Expression Language features available for message interpolation.

This property only affects the EL feature level of "static" constraint violation messages set through the message attribute of constraint annotations.

In particular, it doesn't affect the default EL feature level for custom violations created programmatically in validator implementations. The feature level for those can only be configured directly in the validator implementation.

A regular expression that can be used to exclude some paths from logging.

The log directory to use when logging access to a file If this is not set then the current working directory is used.

If basic auth should be enabled. If both basic and form auth is enabled then basic auth will be enabled in silent mode. If no authentication mechanisms are configured basic auth is the default.

The authentication realm

The encryption key that is used to store persistent logins (e.g. for form auth). Logins are stored in a persistent cookie that is encrypted with AES-256 using a key derived from a SHA-256 hash of the key that is provided here. If no key is provided then an in-memory one will be generated, this will change on every restart though so it is not suitable for production environments. This must be more than 16 characters long for security reasons

A comma-separated list of ContentType to indicate whether a given multipart field should be handled as a file part. You can use this setting to force HTTP-based extensions to parse a message part as a file based on its content type. For now, this setting only works when using RESTEasy Reactive.

The compression level used when compression support is enabled.

The `Access-Control-Allow-Credentials` header is used to tell the browsers to expose the response to front-end JavaScript code when the request’s credentials mode Request.credentials is “include”. The value of this header will default to `true` if `quarkus.http.cors.origins` property is set and there is a match with the precise `Origin` header and that header is not '*'.

The `Access-Control-Max-Age` response header value indicating how long the results of a pre-flight request can be cached.

HTTP headers exposed in CORS Comma separated list of valid headers. ex: X-Custom,Content-Disposition default: empty

HTTP headers allowed for CORS Comma separated list of valid headers. ex: X-Custom,Content-Disposition The filter allows any header if this is not set. default: returns any requested header as valid

HTTP methods allowed for CORS Comma separated list of valid methods. ex: GET,PUT,POST The filter allows any method if this is not set. default: returns any requested method as valid

The number if IO threads used to perform IO. This will be automatically set to a reasonable value based on the number of CPU cores if it is not provided. If this is set to a higher value than the number of Vert.x event loops then it will be capped at the number of event loops. In general this should be controlled by setting quarkus.vertx.event-loops-pool-size, this setting should only be used if you want to limit the number of HTTP io threads to a smaller number than the total number of IO threads.

The maximum number of connections that are allowed at any one time. If this is set it is recommended to set a short idle timeout.

If either this or allow-forwarded are true and proxy address forwarding is enabled then the not standard Forwarded header will be used. In case the standard Forwarded header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with quarkus.http.proxy.allow-x-forwarded has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-*` headers from the client.

The {@linkplain CredentialsProvider}. If this property is configured then a matching 'CredentialsProvider' will be used to get the keystore, keystore key and truststore passwords unless these passwords have already been configured. Please note that using MicroProfile {@linkplain ConfigSource} which is directly supported by Quarkus Configuration should be preferred unless using `CredentialsProvider` provides for some additional security and dynamism.

The credentials provider bean name.

It is the @Named value of the credentials provider bean. It is used to discriminate if multiple CredentialsProvider beans are available. It is recommended to set this property even if there is only one credentials provider currently available to ensure the same provider is always found in deployments where more than one provider may be available.

The file path to a server certificate or certificate chain in PEM format.
@deprecated Use #files instead.

The list of path to server certificates using the PEM format. Specifying multiple files require SNI to be enabled.

The file path to the corresponding certificate private key file in PEM format.
@deprecated Use #keyFiles instead.

The list of path to server certificates private key file using the PEM format. Specifying multiple files require SNI to be enabled. The order of the key files must match the order of the certificates.

An optional key store which holds the certificate information instead of specifying separate files.

An optional parameter to specify type of the key store file. If not given, the type is automatically detected based on the file name.

An optional parameter to select a specific key in the key store. When SNI is disabled, if the key store contains multiple keys and no alias is specified, the behavior is undefined.

An optional parameter to define the password for the key, in case it's different from #keyStorePassword If not given then it may be retrieved from {@linkplain CredentialsProvider}.
@see #credentialsProvider.

A parameter to specify a {@linkplain CredentialsProvider} property key which can be used to get the password for the key from {@linkplain CredentialsProvider}.
@see #credentialsProvider

A parameter to specify the password of the key store file. If not given, and if it can not be retrieved from {@linkplain CredentialsProvider}, then the default ("password") is used.
@see #credentialsProvider

A parameter to specify a {@linkplain CredentialsProvider} property key which can be used to get the password of the key store file from {@linkplain CredentialsProvider}.
@see #credentialsProvider

An optional parameter to specify a provider of the key store file. If not given, the provider is automatically detected based on the key store file type.

An optional parameter to trust only one specific certificate in the trust store (instead of trusting all certificates in the store).

An optional trust store which holds the certificate information of the certificates to trust.

An optional parameter to specify type of the trust store file. If not given, the type is automatically detected based on the file name.

A parameter to specify the password of the trust store file. If not given then it may be retrieved from {@linkplain CredentialsProvider}.
@see #credentialsProvider.

A parameter to specify a {@linkplain CredentialsProvider} property key which can be used to get the password of the trust store file from {@linkplain CredentialsProvider}.
@see #credentialsProvider

An optional parameter to specify a provider of the trust store file. If not given, the provider is automatically detected based on the trust store file type.

The cipher suites to use. If none is given, a reasonable default is selected.

Provides a hint (optional) for the default content type of responses generated for the errors not handled by the application.

If the client requested a supported content-type in request headers (e.g. "Accept: application/json", "Accept: text/html"), Quarkus will use that content type.

Otherwise, it will default to the content type configured here.

The Ide to use to open files from the DevUI. auto means that Quarkus will attempt to determine the Ide being used.

Defines how names of JSON properties ("external names") are derived from names of POJO methods and fields ("internal names"). The value can be one of the one of the constants in com.fasterxml.jackson.databind.PropertyNamingStrategies, so for example, LOWER_CAMEL_CASE or UPPER_CAMEL_CASE. The value can also be a fully qualified class name of a com.fasterxml.jackson.databind.PropertyNamingStrategy subclass.

Define which properties of Java Beans are to be included in serialization.

@deprecated JNI is always enabled starting from GraalVM 19.3.1.

Paths of library to load.

Client secret. Required with a `client_credentials` grant type.

Set to true if Keycloak Admin Client injection is supported.

OAuth 2.0 Access Token Scope.

Keycloak server URL, for example, `https://host:port`. If this property is not set then the Keycloak Admin Client injection will fail - use {@linkplain org.keycloak.admin.client.KeycloakBuilder} to create it instead.

Indicates if the Keycloak realm has to be created when the realm file pointed to by the 'realm-path' property does not exist. Disable it if you'd like to create a realm using Keycloak Administration Console or Keycloak Admin API from {@linkplain io.quarkus.test.common.QuarkusTestResourceLifecycleManager}.

If DevServices has been explicitly enabled or disabled.

When DevServices is enabled Quarkus will attempt to automatically configure and start Keycloak when running in Dev or Test mode and when Docker is running.

Grant type which will be used to acquire a token to test the OIDC 'service' applications

The container image name to use, for container based DevServices providers. Image with a Quarkus based distribution is used by default. Image with a WildFly based distribution can be selected instead, for example: 'quay.io/keycloak/keycloak:19.0.3-legacy'.

Note Keycloak Quarkus and Keycloak WildFly images are initialized differently. By default, Dev Services for Keycloak will assume it is a Keycloak Quarkus image if the image version does not end with a '-legacy' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check.

The JAVA_OPTS passed to the keycloak JVM

If Keycloak-X image is used. By default, Dev Services for Keycloak will assume a Keycloak-X image is used if the image name contains a 'keycloak-x' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check which may be necessary if you build custom Keycloak-X or Keycloak images. You do not need to set this property if the default check works.

Optional fixed port the dev service will listen to.

If not defined, the port will be chosen randomly.

The Keycloak realm name. This property will be used to create the realm if the realm file pointed to by the 'realm-path' property does not exist, default value is 'quarkus' in this case. If the realm file pointed to by the 'realm-path' property exists then it is still recommended to set this property for Dev Services for Keycloak to avoid parsing the realm file in order to determine the realm name.

The comma-separated list of class or file system paths to Keycloak realm files which will be used to initialize Keycloak. The first value in this list will be used to initialize default tenant connection properties.

The value of the quarkus-dev-service-keycloak label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Keycloak looks for a container with the quarkus-dev-service-keycloak label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-keycloak label set to the specified value.

Container sharing is only used in dev mode.

Indicates if the Keycloak container managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Keycloak starts a new container.

The discovery uses the quarkus-dev-service-label label. The value is configured using the service-name property.

Container sharing is only used in dev mode.

Show Keycloak log messages with a "Keycloak:" prefix.

Keycloak start command. Use this property to experiment with Keycloak start options, see https://www.keycloak.org/server/all-config. Note it will be ignored when loading legacy Keycloak WildFly images.

Enables policy enforcement.

Password used to use to connect to the remote dev-mode application

URL used to use to connect to the remote dev-mode application

The names of additional resource files to watch for changes, triggering a reload on change. Directories are not supported.

The names of the handlers to link to this category.

The log level for this category. Note that to get log levels below INFO, the minimum level build time configuration option needs to be adjusted as well.

The minimum log level for this category. By default, all categories are configured with DEBUG minimum level. To get runtime logging below DEBUG, e.g. TRACE, the minimum level has to be adjusted at build time, the right log level needs to be provided at runtime. As an example, to get TRACE logging, minimum level needs to be at TRACE and the runtime log level needs to match that.

Specify whether this logger should send its output to its parent Logger

If the console logging should be in color. If undefined quarkus takes best guess based on operating system and environment. Note that this value will be ignored if an extension is present that takes control of console formatting (e.g. an XML or JSON-format extension). This has been deprecated, and replaced with quarkus.console.color instead, as quarkus now provides more console based functionality than just logging.

The name of the filter to link to the console handler.

The character encoding used

The name of the filter to link to the file handler.

File handler rotation file suffix. When used, the file will be rotated based on its suffix. Example fileSuffix: .yyyy-MM-dd