Skip to main content
Version: v1.9

hydra serve admin

hydra serve admin#

Serves Administrative HTTP/2 APIs

Synopsis#

This command opens one port and listens to HTTP/2 API requests. The exposed API handles administrative requests like managing OAuth 2.0 Clients, JSON Web Keys, login and consent sessions, and others.

This command is configurable using the same options available to "serve public" and "serve all".

It is generally recommended to use this command only if you require granular control over the administrative and public APIs. For example, you might want to run different TLS certificates or CORS settings on the public and administrative API.

This command does not work with the "memory" database. Both services (administrative, public) MUST use the same database connection to be able to synchronize.

Configuration#

ORY Hydra can be configured using environment variables as well as a configuration file. For more information on configuration options, open the configuration documentation:

https://github.com/ory/hydra/blob/undefined/docs/docs/reference/config.md <<

hydra serve admin [flags]

Options#

  -h, --help   help for admin

Options inherited from parent commands#

  -c, --config strings                                   Path to one or more .json, .yaml, .yml, .toml config files. Values are loaded in the order provided, meaning that the last config file overwrites values from the previous config file.      --dangerous-allow-insecure-redirect-urls strings   DO NOT USE THIS IN PRODUCTION - Disable HTTPS enforcement for the provided redirect URLs      --dangerous-force-http                             DO NOT USE THIS IN PRODUCTION - Disables HTTP/2 over TLS (HTTPS) and serves HTTP instead      --sqa-opt-out                                      Disable anonymized telemetry reports - for more information please visit https://www.ory.sh/docs/ecosystem/sqa

SEE ALSO#

  • hydra serve - Parent command for starting public and administrative HTTP/2 APIs