# UMA Service ESS provides a [User Managed Access Grant 2.0 (UMA)](https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-grant-2.0.html) service. This service allows clients to exchange a token or credential in one format for an access token that can be used when interacting with a Pod resource. For example, a client can exchange an OpenID Connect ID token along with one or more Verifiable Credential documents for a single access token. ESS’ UMA service is responsible for handling the [UMA authorization flow](https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-grant-2.0.html#protocol-flow-details-sec). If an agent tries to access a Pod resource on ESS, ESS directs the resource request to the UMA authorization service which checks to see if the agent has the appropriate access privileges: * If the agent does not have the appropriate access privileges, the UMA flow allows for the user to acquire the appropriate access privilege through an iterative exchange (e.g., first with an access grant VC and then with the ID token). These access privileges are enforced with the ACP data model. ## UMA Service Endpoint By default, the ESS UMA Service runs from the following root URL: ```none https://uma. ``` To change the root UMA service URL, see [**`INRUPT_UMA_ISSUER`**](#inrupt_uma_issuer) . ### Discovery ESS provides a metadata resource **`/.well-known/uma2-configuration`** from the root UMA service URL: ```none https://uma./.well-known/uma2-configuration ``` The endpoint returns the current deployment’s UMA service configuration. #### ESS Services with UMA Flow Support The following ESS services support the use of UMA authorization flow: * [Query (QPF) Service](https://docs.inrupt.com/ess/2.3/service-query#access-control), * [Pod Storage Service](https://docs.inrupt.com/ess/2.3/service-pod-management/service-pod-storage#access), and * [Access Grant Service (for its endpoints)](https://docs.inrupt.com/ess/2.3/service-access-grant#access-tokens). The services also support the use of Solid-OpenID Connect (OIDC) access tokens. For QPF Service’s UMA-related configuration, see: * [UMA Configuration](https://docs.inrupt.com/ess/2.3/service-query#qpf-query-service) For Pod Storage Service’s UMA-related configuration, see: * [Pod Storage UMA Configuration](https://docs.inrupt.com/ess/2.3/service-pod-management/service-pod-storage#pod-storage-uma-configuration) . For Access Grant Service’s UMA-related configuration, see: * [UMA Configuration](https://docs.inrupt.com/ess/2.3/service-access-grant#uma-configuration). The services also support the use of Solid-OpenID Connect (OIDC) access tokens. ## Configuration As part of the [installation process](https://docs.inrupt.com/ess/2.3/installation), Inrupt provides base Kustomize overlays and associated files that require deployment-specific configuration inputs. The following configuration options are available for the service and may be set as part of [updating the inputs for your deployment](https://docs.inrupt.com/ess/installation#step-1-initialize-the-installation-directory). The Inrupt-provided base Kustomize overlays may be using updated configuration values that differ from the default values. {% hint style="info" %} **Note**\ Whitespaces are **preserved** when parsing comma-delimited lists (i.e., the parsed string values are not trimmed). For example, when parsed, **`"value1, value2,value3 "`** results in **`"value1"`** , **`" value2"`** , **`"value3 "`** . {% endhint %} ### Required #### INRUPT\_UMA\_ISSUER The URI of the UMA service. See also: * **`INRUPT_AUTHZ_AS_URI`** configuration for [Pod Services](https://docs.inrupt.com/ess/2.3/services/service-pod-management). * **`INRUPT_AUTHZ_AS_URI`** configuration for [Query Service](https://docs.inrupt.com/ess/2.3/services/service-query). * **`INRUPT_AUTHZ_AS_URI`** configuration for [Query Indexer](https://docs.inrupt.com/ess/2.3/services/broken-reference). * **`INRUPT_AUTHZ_AS_URI`** configuration for [Access Grant Service](https://docs.inrupt.com/ess/2.3/services/service-access-grant). #### INRUPT\_UMA\_VC\_VERIFIER The URI of the VC HTTP API verifier. #### QUARKUS\_GRPC\_CLIENTS\_AUTHZ\_HOST The gRPC host of the Authorization Server. #### QUARKUS\_GRPC\_CLIENTS\_AUTHZ\_PORT The gRPC port of the Authorization Server. #### SMALLRYE\_JWT\_SIGN\_KEY\_LOCATION The location of a signing key in JWK format. See also: * [**`SMALLRYE_JWT_ENCRYPT_KEY_LOCATION`**](https://docs.inrupt.com/ess/2.3/service-pod-management/service-pod-storage#smallrye_jwt_encrypt_key_location) configuration for [Pod Storage Service](https://docs.inrupt.com/ess/2.3/services/service-pod-management/service-pod-storage). **Kafka Configuration** {% hint style="info" %} **Tip**\ See also [ESS’ Kafka Configuration](https://docs.inrupt.com/ess/2.3/services/appendix/appendix-kafka-configuration). {% endhint %} #### INRUPT\_KAFKA\_AUDITV1EVENTSENCRYPTED\_CIPHER\_PASSWORD The strong cipher key to use when running auditing with encrypted messages over the **`auditv1eventsencrypted`** topic. #### INRUPT\_KAFKA\_AUDITV1EVENTSPRODUCERENCRYPTED\_CIPHER\_PASSWORD The strong cipher key to use when running auditing with encrypted messages over the **`auditv1eventsproducerencrypted`** topic. #### KAFKA\_BOOTSTRAP\_SERVERS Default : **`localhost:9092`** Comma-delimited list of Kafka broker servers for use by ESS services, including this service. Setting [**`KAFKA_BOOTSTRAP_SERVERS`**](#kafka_bootstrap_servers) configures ESS to use the same Kafka instance(s) for all its Kafka [message channels](https://quarkus.io/guides/kafka#kafka-configuration) (e.g., **`solidresource`** and **`auditv1out`** message channels). This service uses the **`auditv1out`** message channel. {% hint style="info" %} **Note**\ Inrupt-provided overlays default to using [**`KAFKA_BOOTSTRAP_SERVERS`**](#kafka_bootstrap_servers) . To use a different Kafka instance for the **`auditv1out`** channel, use specific [message channel](https://quarkus.io/guides/kafka#kafka-configuration) configuration. {% endhint %} See also [ESS’ Kafka Configuration](https://docs.inrupt.com/ess/2.3/services/appendix/appendix-kafka-configuration). ## Optional **Configuration Logging** ESS services log their startup configuration. #### INRUPT\_LOGGING\_CONFIGURATION\_PREFIX\_ALLOW Default : inrupt,smallrye.jwt.expiration.grace,mp.jwt.verify.clock.skew,smallrye.jwt.always-check-authorization,smallrye.jwt.token.decryption.kid,smallrye.jwt.token.schemes,smallrye.jwt.require.named-principal,smallrye.jwt.time-to-live,smallrye.jwt.jwks.refresh-interval,smallrye.jwt.jwks.forced-refresh-interval,smallrye.jwt.required.claims,mp.jwt.verify.audiences A comma-separated list of configuration property prefixes ( **case-sensitive** ) that determine which configurations are logged: * If the list is empty, NO configuration property is logged. * If a configuration property starts with a listed prefix (case-sensitive), the configuration property and its value are logged unless the configuration also matches a prefix in [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) (which acts as a filter on [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow) list). As such, if the configuration matches prefix in both [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow) and [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny), the [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) takes precedence and the configuration is not logged. For example, if **`inrupt.`** is an allow prefix, but **`inrupt.kafka.`** is a deny prefix, all configurations that start with **`inrupt.kafka.`** are excluded from the logs. When specifying the prefixes, you can specify the prefixes using one of two formats: * using dot notation (e.g., **`inrupt.foobar.`** ), or * using the [MicroProfile Config environmental variables conversion value](https://quarkus.io/guides/config-reference#environment-variables) (e.g., **`INRUPT_FOOBAR_`** ). {% hint style="danger" %} **Warning**\ Use the same format for **both** [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow) and [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) . For example, if you change the format of [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow) , change the format of [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) as well. {% endhint %} {% hint style="info" %} **Tip**\ To avoid allowing more than desired configurations, specify as much of the prefix as possible. If the prefix specifies the complete prefix term, include the term delineator. For example: * If using dot-notation, if you want to match configuration properties of the form **`foobar....`** , specify **`foobar.`** (including the dot **`.`** ) instead of, for example, **`foo`** or **`foobar`** . * If using converted form, if you want to match configuration properties of the form **`FOOBAR_...`** , specify **`FOOBAR_`** (including the underscore **`_`** ) instead of, for example, **`FOO`** or **`FOOBAR`** . {% endhint %} #### INRUPT\_LOGGING\_CONFIGURATION\_PREFIX\_DENY Default : **`inrupt.kafka`** A comma-separated list of configuration name prefixes (case-sensitive) that determines which configurations (that would otherwise match the [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow)) are not logged. That is, [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) acts as a filter on [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow). For example: * If **`foobar.`** is an allowed prefix, to suppress **`foobar.private.`** , you can specify **`foobar.private.`** to the deny list. * If **`foobar.`** is **not** an allowed prefix, no property starting with **`foobar.`** is logged. As such, you do not need to specify **`foobar.private`** to the deny list. When specifying the prefixes, you can specify the prefixes using one of two formats: * using dot notation (e.g., **`inrupt.foobar.`** ), or * using the [MicroProfile Config environmental variables conversion value](https://quarkus.io/guides/config-reference#environment-variables) (e.g., **`INRUPT_FOOBAR_`** ). {% hint style="danger" %} **Warning**\ Use the same format for **both** [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow) and [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) . For example, if you change the format of [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_ALLOW`**](#inrupt_logging_configuration_prefix_allow) , change the format of [**`INRUPT_LOGGING_CONFIGURATION_PREFIX_DENY`**](#inrupt_logging_configuration_prefix_deny) as well. {% endhint %} #### INRUPT\_LOGGING\_REDACTION\_NAME\_ACTION Default : **`REPLACE`** Type of the redaction to perform. Supported values are:
ActionDescription
REPLACEDefault. Replaces the matching text with a specified replacement.
PLAINLeaves the matching field unprocessed. Only available if the redaction target is a field (i.e., INRUPT_LOGGING_REDACTION_{NAME}_FIELD).
DROPSuppresses the matching field. Only available if the redaction target is a field (i.e., INRUPT_LOGGING_REDACTION_{NAME}_FIELD).
PRIORITIZEChanges the log level of the matching message.
SHA256Replaces the matching text with its hash.
* If the action is **`REPLACE`** ( *default* ), see also **`INRUPT_LOGGING_REDACTION_{NAME}_REPLACEMENT`** . * If the action is to **`PRIORITIZE`** , see also **`INRUPT_LOGGING_REDACTION_{NAME}_LEVEL`** . For more information on log redaction, see [Logging Redaction](https://docs.inrupt.com/ess/2.3/administration/logging/logging-redaction). #### INRUPT\_LOGGING\_REDACTION\_NAME\_EXCEPTION Fully qualified name of the exception class to match in the log messages (includes inner exception). Configure to target an exception message class. For more information on log redaction, see [Logging Redaction](https://docs.inrupt.com/ess/2.3/administration/logging/logging-redaction). #### INRUPT\_LOGGING\_REDACTION\_NAME\_FIELD Exact name of the field to match in the log messages. Configure to target a specific log message field for redaction. For more information on log redaction, see [Logging Redaction](https://docs.inrupt.com/ess/2.3/administration/logging/logging-redaction). #### INRUPT\_LOGGING\_REDACTION\_NAME\_LEVEL A new log level to use for the log message if the **`INRUPT_LOGGING_REDACTION_{NAME}_ACTION`** is **`PRIORITIZE`** . #### INRUPT\_LOGGING\_REDACTION\_NAME\_PATTERN A regex (see [Java regex pattern](https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/regex/Pattern.html#sum)) to match in the log messages. Configure to target log message text that matches a specified pattern. For more information on log redaction, see [Logging Redaction](https://docs.inrupt.com/ess/2.3/administration/logging/logging-redaction). #### INRUPT\_LOGGING\_REDACTION\_NAME\_REPLACEMENT Replacement text to use if the **`INRUPT_LOGGING_REDACTION_{NAME}_ACTION`** is **`REPLACE`** . Replacement text to use if the **`INRUPT_LOGGING_REDACTION_{NAME}_ACTION`** is **`REPLACE`** . If unspecified, defaults to **`[REDACTED]`** . For more information on log redaction, see [Logging Redaction](https://docs.inrupt.com/ess/2.3/administration/logging/logging-redaction). #### INRUPT\_AUDIT\_PRODUCER\_REQUEST\_METADATA\_ALLOW A comma-separated list of application-defined properties that can be included in the associated [audit events](https://docs.inrupt.com/ess/2.3/service-auditing#audit-events) (unless specified in the corresponding **`INRUPT_AUDIT_PRODUCER_REQUEST_METADATA_DENY`**). This configuration is **case-sensitive** to the propagated properties in the baggage. {% hint style="info" %} **Tip**\ To include a propagated property that was added via the [**`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**](#inrupt_request_metadata_propagator_header_allow) configuration, ensure that the cases of these properties match. {% endhint %} See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. #### INRUPT\_AUDIT\_PRODUCER\_REQUEST\_METADATA\_DENY A comma-separated list of application-defined properties to exclude from the associated audit messages. This setting takes precedence over **`INRUPT_AUDIT_PRODUCER_REQUEST_METADATA_ALLOW`**. This configuration is **case-sensitive** to the propagated properties in the baggage. {% hint style="info" %} **Tip**\ To exclude a propagated property that was added via the [**`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**](#inrupt_request_metadata_propagator_header_allow) configuration, ensure that the cases of these properties match. {% endhint %} See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/latest/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/latest/administration/application-defined-metadata) for more information. #### INRUPT\_LOGGING\_REQUEST\_METADATA\_ALLOW A comma-separated list of application-defined properties that can be included in the associated [log messages](https://docs.inrupt.com/ess/2.3/administration/logging) (unless specified in the corresponding **`INRUPT_LOGGING_REQUEST_METADATA_DENY`**). This configuration is **case-sensitive** to the propagated properties in the baggage. {% hint style="info" %} **Tip**\ To include a propagated property that was added via the [**`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**](#inrupt_request_metadata_propagator_header_allow) configuration, ensure that the cases of these properties match. {% endhint %} See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. #### INRUPT\_LOGGING\_REQUEST\_METADATA\_DENY A comma-separated list of application-defined properties to exclude from the associated log messages. This setting takes precedence over **`INRUPT_LOGGING_REQUEST_METADATA_ALLOW`**. This configuration is **case-sensitive** to the propagated properties in the baggage. {% hint style="info" %} **Tip**\ To exclude a propagated property that was added via the [**`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**](#inrupt_request_metadata_propagator_header_allow) configuration, ensure that the cases of these properties match. {% endhint %} See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. #### INRUPT\_REQUEST\_METADATA\_PROPAGATOR\_HEADER\_ALLOW A comma-separated list of non-baggage request headers to add to the [baggage](https://www.w3.org/TR/baggage/) (unless specified in the corresponding **`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_DENY`**); i.e., include these non-baggage request headers as application-defined properties. The configuration is case-insensitive; i.e., the listed headers do **not** need to match the case of the client request headers. For example, a list that includes **`x-correlation-id`** can match **`x-correlation-id`** header, **`X-CoRrElAtIoN-Id`** header, etc. See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. #### INRUPT\_REQUEST\_METADATA\_PROPAGATOR\_HEADER\_DENY A comma-separated list of non-baggage request headers to exclude from being added to the [baggage](https://www.w3.org/TR/baggage/); i.e., excludes these headers as application-defined properties. This setting takes precedence over **`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**. The configuration is case-insensitive; i.e., the listed headers do **not** need to match the case of the client request headers. For example, a list that includes **`x-correlation-id`** can match (and exclude) **`x-correlation-id`** header, **`X-CoRrElAtIoN-Id`** header, etc. See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. #### INRUPT\_REQUEST\_METADATA\_PROPAGATOR\_HEADER\_OVERRIDES A flag that determines ESS behavior when metadata property is defined both as a header and as a baggage entry: * If **`true`** ESS updates/overrides the baggage entry with the header value. * If **`false`** (the default), ESS keeps the baggage entry. For details, [Duplicate Property Definition](https://docs.inrupt.com/ess/administration/application-defined-metadata#duplicate-property-definition) #### INRUPT\_REQUEST\_METADATA\_REFLECTOR\_HEADER\_ALLOW A comma-separated list of application-defined properties that can return as response headers (unless specified in the corresponding [**`INRUPT_REQUEST_METADATA_REFLECTOR_HEADER_DENY`**](#inrupt_request_metadata_reflector_header_deny)). This configuration is **case-sensitive** to the propagated properties in the baggage. {% hint style="info" %} Tip * To return a propagated property that was added via the [**`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**](#inrupt_request_metadata_propagator_header_allow) configuration, ensure that the cases of these properties match. * You may need to update **`QUARKUS_HTTP_CORS_EXPOSED_HEADERS`** to extend the list of [CORS-safelisted response headers](https://developer.mozilla.org/en-US/docs/Glossary/CORS-safelisted_response_header) . {% endhint %} See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. #### INRUPT\_REQUEST\_METADATA\_REFLECTOR\_HEADER\_DENY A comma-separated list of application-defined properties to exclude from returning as response headers. This setting takes precedence over **`INRUPT_REQUEST_METADATA_REFLECTOR_HEADER_ALLOW`**. This configuration is **case-sensitive** to the propagated properties in the baggage. {% hint style="info" %} **Tip**\ To exclude a propagated property that was added via the [**`INRUPT_REQUEST_METADATA_PROPAGATOR_HEADER_ALLOW`**](#inrupt_request_metadata_propagator_header_allow) configuration, ensure that the cases of these properties match. {% endhint %} See: * [Manage Application-Defined Metadata Propagation](https://docs.inrupt.com/ess/2.3/installation/customize-configurations/customization-logging/manage-app-defined-metadata) to configure. * [Application-Defined Metadata](https://docs.inrupt.com/ess/2.3/administration/application-defined-metadata) for more information. ## General #### INRUPT\_JSONLD\_CONTEXT\_ALLOW\_LIST Default : **`https://vc.{ESS DOMAIN}/credentials/v1`** A comma-delimited list of trusted JSON-LD context URIs allowed to be dereferenced. The list is in addition to the following contexts (i.e., you do not need to include the following contexts): * **`https://www.w3.org/2018/credentials/v1`** * **`https://schema.inrupt.com/credentials/v1.jsonld`** * **`https://schema.inrupt.com/credentials/v2.jsonld`** * **`https://w3id.org/security/data-integrity/v1`** * **`https://w3id.org/vc-revocation-list-2020/v1`** * **`https://w3id.org/vc/status-list/2021/v1`** * **`https://w3id.org/security/suites/ed25519-2020/v1`** * **`http://www.w3.org/ns/odrl.jsonld`** {% hint style="warning" %} **Recommended**\ If possible, set this configuration value to that of the [Access Grant Service](https://docs.inrupt.com/ess/2.3/services/service-access-grant). Mismatched values may result in the failure to parse access request/grant VCs. {% endhint %} {% hint style="warning" %} **Warning**\ Do **not** set to an empty list (i.e., do not unset this configuration). If empty, any context URI (with the exception of those URIs in [**`INRUPT_JSONLD_CONTEXT_DENY_LIST`**](#inrupt_jsonld_context_deny_list) ) is allowed, including untrusted and malicious contexts. {% endhint %} #### INRUPT\_JSONLD\_CONTEXT\_DENY\_LIST A deny-list of JSON-LD context URIs. URIs listed in this configuration are prevented from being dereferenced. See also: [**`INRUPT_JSONLD_CONTEXT_ALLOW_LIST`**](#inrupt_jsonld_context_allow_list) . #### INRUPT\_JWT\_ALLOWED\_SIGNATURE\_ALGORITHMS Default : **`ES256`, `RS256`** A comma-separated list that specifies the allowed encryption [algorithms](https://www.rfc-editor.org/rfc/rfc7515#section-4.1.1) used to sign ID tokens. #### INRUPT\_JWT\_ISSUER\_ALLOW\_LIST A comma-separated list of trusted issuers of Solid-OIDC tokens. * If unset, the service accepts Solid-OIDC tokens from all issuers with the exception of those in the [**`INRUPT_JWT_ISSUER_DENY_LIST`**](#inrupt_jwt_issuer_deny_list) . * If set, the service accepts only the Solid-OIDC tokens from the issuers in the list with the following exception: * If an issuer is in both [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) and [**`INRUPT_JWT_ISSUER_DENY_LIST`**](#inrupt_jwt_issuer_deny_list), the [**`INRUPT_JWT_ISSUER_DENY_LIST`**](#inrupt_jwt_issuer_deny_list) supersedes the [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) and the issuer is not accepted by ESS. See also [**`INRUPT_JWT_ISSUER_DENY_LIST`**](#inrupt_jwt_issuer_deny_list) . {% hint style="info" %} **Tip**\ Ensure that the UMA service’s [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) is consistent with the **`INRUPT_JWT_ISSUER_ALLOW_LIST`** value set in [ESS Services with UMA Flow Support](#ess-services-with-uma-flow-support) : * [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](https://docs.inrupt.com/ess/2.3/service-pod-management/service-pod-storage#inrupt_jwt_issuer_allow_list) configuration for [Pod Storage Services](https://docs.inrupt.com/ess/2.3/services/service-pod-management/service-pod-storage). * [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](https://docs.inrupt.com/ess/2.3/service-query#inrupt_jwt_issuer_allow_list) configuration for [Query Service](https://docs.inrupt.com/ess/2.3/services/service-query). * [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](https://docs.inrupt.com/ess/2.3/service-access-grant#inrupt_jwt_issuer_allow_list) configuration for [Access Grant Service](https://docs.inrupt.com/ess/2.3/services/service-access-grant). {% endhint %} #### INRUPT\_JWT\_ISSUER\_DENY\_LIST A comma-separated list of disallowed issuers of Solid-OIDC tokens. * If unset, the service accepts Solid-OIDC tokens from all issuers unless [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) is set, in which case, the service only accepts tokens from those in the [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) . * If set, the service disallows the Solid-OIDC tokens from the issuers in the list. If [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) is also set, issuers not in the [**`INRUPT_JWT_ISSUER_ALLOW_LIST`**](#inrupt_jwt_issuer_allow_list) are also disallowed. #### INRUPT\_UMA\_DPOP\_ALGORITHMS Default : **`ES256, RS256`** The permitted DPoP proof algorithms. #### INRUPT\_UMA\_VC\_ISSUER\_ALLOW\_LIST Default : **`https://vc.{ESS_DOMAIN}`** A comma-delimited list of VC issuers accepted by the UMA service. The UMA service uses this value to determine whether to exchange a VC for an UMA access token. For example, ESS’ Access Grant service ( **`https://vc.{ESS_DOMAIN}`** ) issues access requests and access grants as VCs. To have UMA exchange the access requests and grants for UMA tokens, **`INRUPT_UMA_VC_ISSUER_ALLOW_LIST`** has as its default value the ESS’ Access Grant service’s base URL. {% hint style="warning" %} **Warning**\ Issuers in this list are **fully** trusted to issue any type of VC. * For security reasons, do not unset the configuration property. If unset, the UMA service accepts all VC issuers; i.e., UMA service will issue an UMA access token in exchange for VCs from any issuer. * List only trusted issuers. Otherwise, a malicious issuer could issue a VC on behalf of any user without their knowledge or consent, and exchange it for a UMA token. {% endhint %} #### INRUPT\_UMA\_VC\_REVOCATION\_LIST\_CREDENTIAL\_ALLOW\_LIST Default : *unset* A comma-delimited list of permitted domains for VC revocation list credentials. If unset, the service accepts all domains. (Default) #### INRUPT\_UMA\_VC\_VERIFICATION\_METHOD\_ALLOW\_LIST Default : *unset* A comma-delimited list of permitted domains for VC verification methods and corresponding public keys. If unset, the service accepts all domains. (Default) #### INRUPT\_VC\_ISSUER The discoverable issuer of verifiable credentials. #### QUARKUS\_LOG\_LEVEL Default : **`INFO`** Logging level. #### SMALLRYE\_JWT\_NEW\_TOKEN\_LIFESPAN Default : **`300`** The number of seconds that tokens will live. ### Additional Information See also [Quarkus Configuration Options](https://quarkus.io/guides/all-config) .