AGATE Configuration

If undefined, then the pattern is matched against the path. Use query.{param}, where {param} is the parameter value, to use a query parameter. Use query.{param}.url.path|query if the param value is a url and that you want to target the path or query of that url.

Regex pattern to match the URL part of interest in order to extract the collection name and the item id with the keywords '' and ''. E.g. (?P[^/]+)/items/(?P[^/]+)/assets/overview

The location in the request containing the JWT parameter

The name of the parameter containing the JWT

Access is allowed if one of the rule is matching the URL part of interest and if the user has access to the corresponding ARLAS Item.

Access is allowed if one of the rule is matching the URL part of interest. No access control is done.

Agate endpoint prefix

ARLAS URL Search (ex http://arlas-server:9999/arlas/explore/{collection}/_search?f=id:eq:{item})

The header to be forwarded to ARLAS

Agate service connection host

The header containing the method

Agate service port

Dictionary of service name/definition. A service protects an endpoint that is exposing resources linked to an ARLAS Item. The service definition tells how to extract the collection name and the item id that are then used for checking with ARLAS whether the item is accessible or not.

URL Role Based Access Control Definition. A user access an endpoint if one of his role is configured in the role configuration file for the requested endpoint (roles.yaml)

The header containing the requested URL

Must be provided for production.

Expected audience in the JWT. If not set, no audience verification is done.

The name of the header parameter containing the JWT

File location containing the roles

Definition of the endpoints and of the authorized roles. This is automatically filled from role_file

Whether to verify the JWT signature. Should be True in production.

Whether to verify SSL certificates when fetching the OpenID configuration and JWKS. Should be True in production.