latest--config
shared| Type | object |
|---|---|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/ory-hydra-configuration/_shared/latest--config.json |
| Parent schema | ory-hydra-configuration |
Properties
Configures the database connection
1 nested properties
Ignore scan errors when columns in the SQL result have no fields in the destination struct
Configures the logger
4 nested properties
Sets the log level.
Logs sensitive values such as cookie and URL parameter.
Text to use, when redacting sensitive log value.
Sets the log format.
Controls the configuration for the http(s) daemon(s).
4 nested properties
Controls the public daemon serving public API endpoints like /oauth2/auth, /oauth2/token, /.well-known/jwks.json
6 nested properties
The interface or unix socket Ory Hydra should listen and handle public API requests on. Use the prefix unix: to specify a path to a unix socket. Leave empty to listen on all interfaces.
Configures Cross Origin Resource Sharing for public endpoints.
8 nested properties
Sets whether CORS is enabled.
A list of origins a cross-domain request can be executed from. If the special * value is present in the list, all origins will be allowed. An origin may contain a wildcard (*) to replace 0 or more characters (i.e.: http://*.domain.com). Only one wildcard can be used per origin.
[]
A list of HTTP methods the user agent is allowed to use with cross-domain requests.
[
"POST",
"GET",
"PUT",
"PATCH",
"DELETE",
"CONNECT",
"HEAD",
"OPTIONS",
"TRACE"
]
A list of non simple headers the client is allowed to use with cross-domain requests.
[
"Accept",
"Content-Type",
"Content-Length",
"Accept-Language",
"Content-Language",
"Authorization"
]
Sets which headers are safe to expose to the API of a CORS API specification.
[
"Cache-Control",
"Expires",
"Last-Modified",
"Pragma",
"Content-Length",
"Content-Language",
"Content-Type"
]
Sets whether the request can include user credentials like cookies, HTTP authentication or client side SSL certificates.
Sets how long (in seconds) the results of a preflight request can be cached. If set to 0, every request is preceded by a preflight request.
Adds additional log output to debug server side CORS issues.
Sets the permissions of the unix socket
3 nested properties
Owner of unix socket. If empty, the owner will be the user running hydra.
Group of unix socket. If empty, the group will be the primary group of the user running hydra.
Mode of unix socket in numeric form
Access Log configuration for public server.
1 nested properties
Disable access log for health endpoints.
Configures HTTPS (HTTP over TLS). If configured, the server automatically supports HTTP/2.
4 nested properties
Setting enabled to false drops the TLS requirement for the admin endpoint, even if TLS is enabled on the public endpoint.
Whitelist one or multiple CIDR address ranges and allow them to terminate TLS connections. Be aware that the X-Forwarded-Proto header must be set and must never be modifiable by anyone but your proxy / gateway / load balancer. Supports ipv4 and ipv6. Hydra serves http instead of https when this option is set.
6 nested properties
The interface or unix socket Ory Hydra should listen and handle administrative API requests on. Use the prefix unix: to specify a path to a unix socket. Leave empty to listen on all interfaces.
Configures Cross Origin Resource Sharing for public endpoints.
8 nested properties
Sets whether CORS is enabled.
A list of origins a cross-domain request can be executed from. If the special * value is present in the list, all origins will be allowed. An origin may contain a wildcard (*) to replace 0 or more characters (i.e.: http://*.domain.com). Only one wildcard can be used per origin.
[]
A list of HTTP methods the user agent is allowed to use with cross-domain requests.
[
"POST",
"GET",
"PUT",
"PATCH",
"DELETE",
"CONNECT",
"HEAD",
"OPTIONS",
"TRACE"
]
A list of non simple headers the client is allowed to use with cross-domain requests.
[
"Accept",
"Content-Type",
"Content-Length",
"Accept-Language",
"Content-Language",
"Authorization"
]
Sets which headers are safe to expose to the API of a CORS API specification.
[
"Cache-Control",
"Expires",
"Last-Modified",
"Pragma",
"Content-Length",
"Content-Language",
"Content-Type"
]
Sets whether the request can include user credentials like cookies, HTTP authentication or client side SSL certificates.
Sets how long (in seconds) the results of a preflight request can be cached. If set to 0, every request is preceded by a preflight request.
Adds additional log output to debug server side CORS issues.
Sets the permissions of the unix socket
3 nested properties
Owner of unix socket. If empty, the owner will be the user running hydra.
Group of unix socket. If empty, the group will be the primary group of the user running hydra.
Mode of unix socket in numeric form
Access Log configuration for admin server.
1 nested properties
Disable access log for health endpoints.
Configures HTTPS (HTTP over TLS). If configured, the server automatically supports HTTP/2.
4 nested properties
Setting enabled to false drops the TLS requirement for the admin endpoint, even if TLS is enabled on the public endpoint.
Whitelist one or multiple CIDR address ranges and allow them to terminate TLS connections. Be aware that the X-Forwarded-Proto header must be set and must never be modifiable by anyone but your proxy / gateway / load balancer. Supports ipv4 and ipv6. Hydra serves http instead of https when this option is set.
5 nested properties
Specify the SameSite mode that cookies should be sent with.
Some older browser versions don’t work with SameSite=None. This option enables the workaround defined in https://web.dev/samesite-cookie-recipes/ which essentially stores a second cookie without SameSite as a fallback.
Sets the cookie domain for session and CSRF cookies. Useful when dealing with subdomains. Use with care!
Sets the HTTP Cookie secure flag in development mode. HTTP Cookies always have the secure flag in production mode.
Sets the session cookie name. Use with care!
3 nested properties
Sets the data source name. This configures the backend where Ory Hydra persists data. If dsn is memory, data will be written to memory and is lost when you restart this instance. Ory Hydra supports popular SQL databases. For more detailed configuration information go to: https://www.ory.sh/docs/hydra/dependencies-environment#sql
Configure how outgoing network calls behave.
1 nested properties
Configure how outgoing HTTP calls behave.
1 nested properties
Disallow all outgoing HTTP calls to private IP ranges. This feature can help protect against SSRF attacks.
Configures Hardware Security Module.
6 nested properties
Full path (including file extension) of the HSM vendor PKCS#11 library
PIN code for token operations
Slot ID of the token to use (if label is not specified)
Label of the token to use (if slot is not specified). If both slot and label are set, token label takes preference over slot. In this case first slot, that contains this label is used.
Key set prefix can be used in case of multiple Ory Hydra instances need to store keys on the same HSM partition. For example if hsm.key_set_prefix=app1. then key set hydra.openid.id-token would be generated/requested/deleted on HSM with CKA_LABEL=app1.hydra.openid.id-token.
Configures ./well-known/ settings.
2 nested properties
Configures the /.well-known/jwks.json endpoint.
1 nested properties
A list of JSON Web Keys that should be exposed at that endpoint. This is usually the public key for verifying OpenID Connect ID Tokens. However, you might want to add additional keys here as well.
[
"hydra.openid.id-token"
]
Configures OpenID Connect Discovery (/.well-known/openid-configuration).
7 nested properties
Overwrites the JWKS URL
Overwrites the OAuth2 Token URL
Overwrites the OAuth2 Auth URL
Sets the OpenID Connect Dynamic Client Registration Endpoint
A list of supported claims to be broadcasted. Claim sub is always included.
The scope OAuth 2.0 Clients may request. Scope offline, offline_access, and openid are always included.
A URL of the userinfo endpoint to be advertised at the OpenID Connect Discovery endpoint /.well-known/openid-configuration. Defaults to Ory Hydra's userinfo endpoint at /userinfo. Set this value if you want to handle this endpoint yourself.
Configures OpenID Connect features.
2 nested properties
Configures the Subject Identifier algorithm. For more information please head over to the documentation: https://www.ory.sh/docs/hydra/advanced#subject-identifier-algorithms
2 nested properties
A list of algorithms to enable.
[
"public"
]
Configures the pairwise algorithm.
1 nested properties
Configures OpenID Connect Dynamic Client Registration (exposed as admin endpoints /clients/...).
2 nested properties
Enable dynamic client registration.
The OpenID Connect Dynamic Client Registration specification has no concept of whitelisting OAuth 2.0 Scope. If you want to expose Dynamic Client Registration, you should set the default scope enabled for newly registered clients. Keep in mind that users can overwrite this default by setting the scope key in the registration payload, effectively disabling the concept of whitelisted scopes.
6 nested properties
3 nested properties
This value will be used as the issuer in access and ID tokens. It must be specified and using HTTPS protocol, unless --dev is set. This should typically be equal to the public value.
This is the base location of the public endpoints of your Ory Hydra installation. This should typically be equal to the issuer value. If left unspecified, it falls back to the issuer value.
This is the base location of the admin endpoints of your Ory Hydra installation.
Sets the OAuth2 Login Endpoint URL of the OAuth2 User Login & Consent flow. Defaults to an internal fallback URL showing an error.
Sets the consent endpoint of the User Login & Consent flow. Defaults to an internal fallback URL showing an error.
Sets the logout endpoint. Defaults to an internal fallback URL showing an error.
Sets the error endpoint. The error ui will be shown when an OAuth2 error occurs that which can not be sent back to the client. Defaults to an internal fallback URL showing an error.
When a user agent requests to logout, it will be redirected to this url afterwards per default.
2 nested properties
Defines how scopes are matched. For more details have a look at https://github.com/ory/fosite#scopes
Defines access token type. jwt is a bad idea, see https://www.ory.sh/docs/hydra/advanced#json-web-tokens
Configures time to live.
5 nested properties
Configures how long refresh tokens are valid. Set to -1 for refresh tokens to never expire.
9 nested properties
Set this to true if you want to share error debugging information with your OAuth 2.0 clients. Keep in mind that debug information is very valuable when dealing with errors, but might also expose database error codes and similar errors.
1 nested properties
If set to true (default) Ory Hydra encrypt OAuth2 and OpenID Connect session data using AES-GCM and the system secret before persisting it in the database.
Set to true if you want to exclude claim nbf (not before) part of access token.
A list of custom claims which are allowed to be added top level to the Access Token. They cannot override reserved claims.
Configures hashing algorithms. Supports only BCrypt and PBKDF2 at the moment.
3 nested properties
One of the values: pbkdf2, bcrypt.
Warning! This value can not be changed once set as all existing OAuth 2.0 Clients will not be able to sign in any more.
Configures the BCrypt hashing algorithm used for hashing OAuth 2.0 Client Secrets.
1 nested properties
Sets the BCrypt cost. The higher the value, the more CPU time is being used to generate hashes.
Configures the PBKDF2 hashing algorithm used for hashing OAuth 2.0 Client Secrets.
1 nested properties
Sets the PBKDF2 iterations. The higher the value, the more CPU time is being used to generate hashes.
2 nested properties
Sets whether PKCE should be enforced for all clients.
Sets whether PKCE should be enforced for public clients.
1 nested properties
Automatically grant authorized OAuth2 Scope in OAuth2 Client Credentials Flow. Each OAuth2 Client is allowed to request a predefined OAuth2 Scope (for example read write). If this option is enabled, the full
scope is automatically granted when performing the OAuth2 Client Credentials flow.
If disabled, the OAuth2 Client has to request the scope in the OAuth2 request by providing the scope query parameter. Setting this option to true is common if you need compatibility with MITREid.
1 nested properties
Authorization Grants using JWT configuration
3 nested properties
Configures if the JSON Web Token ID (jti) claim is required in the JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants (RFC7523). If set to false, the jti claim is required. Set this value to true only after careful consideration.
Configures if the issued at (iat) claim is required in the JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants (RFC7523). If set to false, the iat claim is required. Set this value to true only after careful consideration.
Configures what the maximum age of a JWT assertion used in the JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants (RFC7523) can be. This feature uses the exp claim and iat claim to calculate assertion age. Assertions exceeding the max age will be denied. Useful as a safety measure and recommended to keep below 720h. This governs the grant.jwt.max_ttl setting.
Sets the refresh token hook endpoint. If set it will be called during token refresh to receive updated token claims.
The secrets section configures secrets used for encryption and signing of several systems. All secrets can be rotated, for more information on this topic go to: https://www.ory.sh/docs/hydra/advanced#rotation-of-hmac-token-signing-and-database-and-cookie-encryption-keys
2 nested properties
The system secret must be at least 16 characters long. If none is provided, one will be generated. They key is used to encrypt sensitive data using AES-GCM (256 bit) and validate HMAC signatures. The first item in the list is used for signing and encryption. The whole list is used for verifying signatures and decryption.
A secret that is used to encrypt cookie sessions. Defaults to secrets.system. It is recommended to use a separate secret in production. The first item in the list is used for signing and encryption. The whole list is used for verifying signatures and decryption.
Enables profiling if set. For more details on profiling, head over to: https://blog.golang.org/profiling-go-programs
Ory Hydra supports distributed tracing.
3 nested properties
Set this to the tracing backend you wish to use. Supports Jaeger, Zipkin DataDog, Elastic APM and Instana. If omitted or empty, tracing will be disabled. Use environment variables to configure DataDog (see https://docs.datadoghq.com/tracing/setup/go/#configuration).
Specifies the service name to use on the tracer.
2 nested properties
Configures the jaeger tracing backend.
4 nested properties
The address of the jaeger-agent where spans should be sent to.
The tracing header format
The value passed to the max tag value length that has been configured.
Configures the zipkin tracing backend.
1 nested properties
The address of Zipkin server where spans should be sent to.
Software Quality Assurance telemetry configuration section
1 nested properties
Disables anonymized telemetry reports - for more information please visit https://www.ory.sh/docs/ecosystem/sqa
SemVer according to https://semver.org/ prefixed with v as in our releases.
Ory Hydra can respect Linux container CPU quota
1 nested properties
Configures parameters using cgroups v1 hierarchy
1 nested properties
Set GOMAXPROCS automatically according to cgroups limits
If true, disables critical security measures to allow easier local development. Do not use in production.
Definitions
The port to listen on.
Sets the permissions of the unix socket
Owner of unix socket. If empty, the owner will be the user running hydra.
Group of unix socket. If empty, the group will be the primary group of the user running hydra.
Mode of unix socket in numeric form
Configures Cross Origin Resource Sharing for public endpoints.
Sets whether CORS is enabled.
A list of origins a cross-domain request can be executed from. If the special * value is present in the list, all origins will be allowed. An origin may contain a wildcard (*) to replace 0 or more characters (i.e.: http://*.domain.com). Only one wildcard can be used per origin.
[]
A list of HTTP methods the user agent is allowed to use with cross-domain requests.
[
"POST",
"GET",
"PUT",
"PATCH",
"DELETE",
"CONNECT",
"HEAD",
"OPTIONS",
"TRACE"
]
A list of non simple headers the client is allowed to use with cross-domain requests.
[
"Accept",
"Content-Type",
"Content-Length",
"Accept-Language",
"Content-Language",
"Authorization"
]
Sets which headers are safe to expose to the API of a CORS API specification.
[
"Cache-Control",
"Expires",
"Last-Modified",
"Pragma",
"Content-Length",
"Content-Language",
"Content-Type"
]
Sets whether the request can include user credentials like cookies, HTTP authentication or client side SSL certificates.
Sets how long (in seconds) the results of a preflight request can be cached. If set to 0, every request is preceded by a preflight request.
Adds additional log output to debug server side CORS issues.
CIDR address range.
"127.0.0.1/32"
"1h""1h5m1s"
Configures HTTPS (HTTP over TLS). If configured, the server automatically supports HTTP/2.
Setting enabled to false drops the TLS requirement for the admin endpoint, even if TLS is enabled on the public endpoint.
Whitelist one or multiple CIDR address ranges and allow them to terminate TLS connections. Be aware that the X-Forwarded-Proto header must be set and must never be modifiable by anyone but your proxy / gateway / load balancer. Supports ipv4 and ipv6. Hydra serves http instead of https when this option is set.