hydra

The most scalable and customizable OpenID Certified™ OpenID Connect and OAuth Provider on the market. Become an OpenID Connect and OAuth2 Provider over night. Broad support for related RFCs. Written in Go, cloud native, headless, API-first. Available as a service on Ory Network and for self-hosters.

15,556

1,492

15,556

105

View on GitHub

Top Related Projects

keycloak

22,126

Open Source Identity and Access Management For Modern Applications and Services

oauth2-proxy

9,631

A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.

node-oidc-provider

3,206

OpenID Certified™ OAuth 2.0 Authorization Server implementation for Node.js

authelia

21,425

The Single Sign-On Multi-Factor portal for web apps

supertokens-core

12,980

Open source alternative to Auth0 / Firebase Auth / AWS Cognito

zitadel

8,619

ZITADEL - Identity infrastructure, simplified for you.

Quick Overview

Ory Hydra is an OAuth 2.0 and OpenID Connect Provider. It's designed to be a secure, high-performance, and cloud-native implementation that integrates easily with existing systems. Hydra focuses on OAuth 2.0 and OpenID Connect without forcing you to use a specific identity provider or user management system.

Pros

Highly scalable and designed for cloud-native environments
Supports all OAuth 2.0 and OpenID Connect flows
Provides robust security features and follows best practices
Easy integration with existing identity providers and user management systems

Cons

Steep learning curve for beginners in OAuth 2.0 and OpenID Connect
Requires additional components for a complete identity management solution
Documentation can be overwhelming due to the complexity of the system
May be overkill for simple authentication needs

Code Examples

Creating an OAuth 2.0 Client:

import "github.com/ory/hydra-client-go/client/admin"

client := admin.NewCreateOAuth2ClientParams().WithBody(&models.OAuth2Client{
    ClientID:      "my-client",
    ClientSecret:  "secret",
    GrantTypes:    []string{"authorization_code", "refresh_token"},
    ResponseTypes: []string{"code", "id_token"},
    Scope:         "openid profile email",
    RedirectURIs:  []string{"https://my-app.com/callback"},
})

_, err := hydraAdmin.CreateOAuth2Client(client)

Initiating an OAuth 2.0 Authorization Code Flow:

import "github.com/ory/hydra-client-go/client/public"

challenge, err := hydraPublic.InitializeLoginFlow(&public.InitializeLoginFlowParams{
    ClientID:    "my-client",
    RedirectURI: "https://my-app.com/callback",
    Scope:       "openid profile email",
    State:       "random-state-string",
})

Introspecting an OAuth 2.0 Access Token:

import "github.com/ory/hydra-client-go/client/admin"

result, err := hydraAdmin.IntrospectOAuth2Token(&admin.IntrospectOAuth2TokenParams{
    Token: accessToken,
})

if result.Payload.Active {
    // Token is valid
    fmt.Printf("Token belongs to subject: %s\n", result.Payload.Sub)
}

Getting Started

Install Ory Hydra:
```
docker pull oryd/hydra:v2.1.1
```

Run Ory Hydra:

docker run -p 4444:4444 -p 4445:4445 \
  -e DSN=memory \
  -e URLS_SELF_ISSUER=https://my-hydra.com/ \
  -e URLS_LOGIN=https://my-login.com/login \
  -e URLS_CONSENT=https://my-consent.com/consent \
  oryd/hydra:v2.1.1 serve all --dangerous-force-http

Create an OAuth 2.0 Client:

hydra clients create \
  --endpoint http://127.0.0.1:4445 \
  --id my-client \
  --secret secret \
  --grant-types authorization_code,refresh_token \
  --response-types code,id_token \
  --scope openid,offline \
  --callbacks http://127.0.0.1:5555/callback

Competitor Comparisons

keycloak

22,126

Open Source Identity and Access Management For Modern Applications and Services

Pros of Keycloak

More comprehensive out-of-the-box features, including user management and admin console
Easier setup and configuration for non-technical users
Broader ecosystem with extensive documentation and community support

Cons of Keycloak

Higher resource consumption and slower performance
Less flexibility for custom integrations and modifications
Steeper learning curve for advanced customizations

Code Comparison

Hydra (Go):

import "github.com/ory/hydra/client"

c := client.NewHTTPClientWithConfig(nil, &client.TransportConfig{
    Schemes:  []string{"http", "https"},
    Host:     "localhost:4444",
    BasePath: "/",
})

Keycloak (Java):

import org.keycloak.admin.client.Keycloak;

Keycloak keycloak = Keycloak.getInstance(
    "http://localhost:8080/auth",
    "master",
    "admin",
    "password",
    "admin-cli");

Both examples show client initialization, but Hydra's approach is more lightweight and focused on HTTP transport, while Keycloak's includes authentication details for the admin client.

oauth2-proxy

9,631

A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.

Pros of oauth2-proxy

Simpler setup and configuration for basic OAuth2 authentication scenarios
Lightweight and focused on proxying requests with OAuth2 authentication
Supports multiple providers out of the box (Google, GitHub, Azure, etc.)

Cons of oauth2-proxy

Limited functionality compared to Hydra's full OAuth2 and OpenID Connect server capabilities
Less flexibility for complex authentication and authorization scenarios
Fewer built-in features for token management and introspection

Code Comparison

oauth2-proxy configuration example:

oauth2_proxy:
  config:
    provider: "github"
    client_id: "your_client_id"
    client_secret: "your_client_secret"
    cookie_secret: "random_string"
    email_domains:
      - "*"

Hydra configuration example:

dsn: memory
serve:
  public:
    port: 4444
  admin:
    port: 4445
strategies:
  access_token: jwt

While oauth2-proxy focuses on simple proxy configuration with OAuth2 authentication, Hydra provides a more comprehensive OAuth2 and OpenID Connect server setup with additional features and flexibility.

node-oidc-provider

3,206

OpenID Certified™ OAuth 2.0 Authorization Server implementation for Node.js

Pros of node-oidc-provider

Lightweight and flexible, allowing for easy customization
Extensive documentation and examples for various use cases
Built specifically for Node.js, providing seamless integration with Node-based applications

Cons of node-oidc-provider

Less out-of-the-box features compared to Hydra
May require more configuration and setup for complex scenarios
Limited built-in support for some advanced OAuth 2.0 flows

Code Comparison

node-oidc-provider:

const Provider = require('oidc-provider');
const configuration = {
  clients: [{ client_id: 'foo', client_secret: 'bar', redirect_uris: ['http://localhost:8080/cb'] }],
};
const oidc = new Provider('http://localhost:3000', configuration);

Hydra:

import "github.com/ory/hydra/driver"

d := driver.NewDefaultDriver()
r := d.Registry()
h := r.OAuth2Handler()

Both examples show basic setup, but node-oidc-provider's configuration is more straightforward for simple use cases, while Hydra's setup demonstrates its modular architecture.

authelia

21,425

The Single Sign-On Multi-Factor portal for web apps

Pros of Authelia

All-in-one authentication and authorization solution
Simpler setup and configuration for basic use cases
Built-in web portal for user management and self-service

Cons of Authelia

Less flexible for complex, distributed architectures
Fewer advanced features compared to Hydra's OAuth2 and OpenID Connect capabilities
Smaller community and ecosystem

Code Comparison

Authelia configuration (YAML):

authentication_backend:
  file:
    path: /config/users_database.yml
access_control:
  default_policy: deny
  rules:
    - domain: secure.example.com
      policy: two_factor

Hydra configuration (YAML):

dsn: postgres://user:password@host:port/database
serve:
  public:
    port: 4444
  admin:
    port: 4445
strategies:
  access_token: jwt

Both projects use YAML for configuration, but Authelia's setup is more straightforward for basic authentication scenarios. Hydra's configuration reflects its focus on OAuth2 and OpenID Connect, with separate public and admin interfaces.

Authelia is better suited for smaller, self-hosted projects requiring simple authentication, while Hydra excels in complex, distributed systems with advanced OAuth2 and OpenID Connect requirements.

supertokens-core

12,980

Open source alternative to Auth0 / Firebase Auth / AWS Cognito

Pros of SuperTokens

Easier setup and integration with pre-built UI components and SDKs
More comprehensive user management features out-of-the-box
Better documentation and community support for developers

Cons of SuperTokens

Less flexible for complex, custom authentication flows
Smaller ecosystem and fewer third-party integrations
More opinionated architecture, which may not suit all project requirements

Code Comparison

SuperTokens (Node.js example):

import supertokens from "supertokens-node";
import Session from "supertokens-node/recipe/session";

supertokens.init({
    appInfo: {
        apiDomain: "https://api.example.com",
        appName: "MyApp",
        websiteDomain: "https://example.com"
    },
    recipeList: [Session.init()]
});

Hydra (Go example):

import "github.com/ory/hydra-client-go"

configuration := hydra.NewConfiguration()
configuration.Servers = hydra.ServerConfigurations{
    {URL: "https://your-hydra-instance.com/"},
}
client := hydra.NewAPIClient(configuration)

Both projects offer robust authentication and authorization solutions, but SuperTokens focuses more on user management and ease of use, while Hydra provides greater flexibility for complex OAuth2 and OpenID Connect scenarios. The choice between them depends on specific project requirements and developer preferences.

zitadel

8,619

ZITADEL - Identity infrastructure, simplified for you.

Pros of Zitadel

All-in-one identity management solution with built-in user management, authentication, and authorization
Offers a user-friendly web interface for easy management and configuration
Supports multiple deployment options, including self-hosted and cloud-based solutions

Cons of Zitadel

Less flexible than Hydra for custom integrations and specific use cases
Newer project with a smaller community and ecosystem compared to Hydra
May have a steeper learning curve for developers familiar with more traditional OAuth2 servers

Code Comparison

Hydra (Go):

import "github.com/ory/hydra/client"

c := client.NewHTTPClientWithConfig(nil, &client.TransportConfig{
    Schemes:  []string{"http", "https"},
    Host:     "localhost:4444",
    BasePath: "/",
})

Zitadel (Go):

import "github.com/zitadel/zitadel/pkg/client/zitadel"

client, err := zitadel.NewClient(
    zitadel.WithClientID("client-id"),
    zitadel.WithClientSecret("client-secret"),
    zitadel.WithEndpoint("https://instance.zitadel.cloud"),
)

Both repositories provide OAuth2 and OpenID Connect capabilities, but Zitadel offers a more comprehensive identity management solution out of the box. Hydra focuses on being a lightweight and flexible OAuth2 server, while Zitadel provides additional features like user management and a web interface. The choice between the two depends on specific project requirements and the desired level of customization.

Convert designs to code with AI

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

Chat | Discussions | Newsletter

Guide | API Docs | Code Docs

Support this project!

Work in Open Source, Ory is hiring!

Ory Hydra is a hardened, OpenID Certified OAuth 2.0 Server and OpenID Connect Provider optimized for low-latency, high throughput, and low resource consumption. Ory Hydra is not an identity provider (user sign up, user login, password reset flow), but connects to your existing identity provider through a login and consent app. Implementing the login and consent app in a different language is easy, and exemplary consent apps (Node) and SDKs for common languages are provided.

Ory Hydra can use Ory Kratos as its identity server.

Ory Hydra on the Ory Network

The Ory Network is the fastest, most secure and worry-free way to use Ory's Services. Ory OAuth2 & OpenID Connect is powered by the Ory Hydra open source federation server, and it's fully API-compatible.

The Ory Network provides the infrastructure for modern end-to-end security:

Identity & credential management scaling to billions of users and devices
Registration, Login and Account management flows for passkey, biometric, social, SSO and multi-factor authentication
Pre-built login, registration and account management pages and components
OAuth2 and OpenID provider for single sign on, API access and machine-to-machine authorization
Low-latency permission checks based on Google's Zanzibar model and with built-in support for the Ory Permission Language

It's fully managed, highly available, developer & compliance-friendly!

GDPR-friendly secure storage with data locality
Cloud-native APIs, compatible with Ory's Open Source servers
Comprehensive admin tools with the web-based Ory Console and the Ory Command Line Interface (CLI)
Extensive documentation, straightforward examples and easy-to-follow guides
Fair, usage-based pricing

Ory Network Hybrid Support Plan

Ory offers a support plan for Ory Network Hybrid, including Ory on private cloud deployments. If you have a self-hosted solution and would like help, consider a support plan! The team at Ory has years of experience in cloud computing. Ory's offering is the only official program for qualified support from the maintainers. For more information see the website or book a meeting!

Get Started

You can use Docker to run Ory Hydra locally or use the Ory CLI to try out Ory Hydra:

# This example works best in Bash
bash <(curl https://raw.githubusercontent.com/ory/meta/master/install.sh) -b . ory
sudo mv ./ory /usr/local/bin/

# Or with Homebrew installed
brew install ory/tap/cli

create a new project (you may also use Docker)

ory create project --name "Ory Hydra 2.0 Example"
project_id="{set to the id from output}"

and follow the quick & easy steps below.

OAuth 2.0 Client Credentials / Machine-to-Machine

Create an OAuth 2.0 Client, and run the OAuth 2.0 Client Credentials flow:

ory create oauth2-client --project $project_id \
    --name "Client Credentials Demo" \
    --grant-type client_credentials
client_id="{set to client id from output}"
client_secret="{set to client secret from output}"

ory perform client-credentials --client-id=$client_id --client-secret=$client_secret --project $project_id
access_token="{set to access token from output}"

ory introspect token $access_token --project $project_id

OAuth 2.0 Authorize Code + OpenID Connect

Try out the OAuth 2.0 Authorize Code grant right away!

By accepting permissions openid and offline_access at the consent screen, Ory refreshes and OpenID Connect ID token,

ory create oauth2-client --project $project_id \
    --name "Authorize Code with OpenID Connect Demo" \
    --grant-type authorization_code,refresh_token \
    --response-type code \
    --redirect-uri http://127.0.0.1:4446/callback
code_client_id="{set to client id from output}"
code_client_secret="{set to client secret from output}"

ory perform authorization-code \
    --project $project_id \
    --client-id $code_client_id \
    --client-secret $code_client_secret
code_access_token="{set to access token from output}"

ory introspect token $code_access_token --project $project_id

What is Ory Hydra?
Quickstart
- Installation
Ecosystem
Security
- Disclosing vulnerabilities
Benchmarks
Telemetry
Documentation
Libraries and third-party projects

What is Ory Hydra?

Ory Hydra is a server implementation of the OAuth 2.0 authorization framework and the OpenID Connect Core 1.0. Existing OAuth2 implementations usually ship as libraries or SDKs such as node-oauth2-server or Ory Fosite, or as fully featured identity solutions with user management and user interfaces, such as Keycloak.

Implementing and using OAuth2 without understanding the whole specification is challenging and prone to errors, even when SDKs are being used. The primary goal of Ory Hydra is to make OAuth 2.0 and OpenID Connect 1.0 better accessible.

Ory Hydra implements the flows described in OAuth2 and OpenID Connect 1.0 without forcing you to use a "Hydra User Management" or some template engine or a predefined front-end. Instead, it relies on HTTP redirection and cryptographic methods to verify user consent allowing you to use Ory Hydra with any authentication endpoint, be it Ory Kratos, authboss, User Frosting or your proprietary Java authentication.

Who's using it?

The Ory community stands on the shoulders of individuals, companies, and maintainers. The Ory team thanks everyone involved - from submitting bug reports and feature requests, to contributing patches and documentation. The Ory community counts more than 33.000 members and is growing rapidly. The Ory stack protects 60.000.000.000+ API requests every month with over 400.000+ active service nodes. None of this would have been possible without each and everyone of you!

The following list represents companies that have accompanied us along the way and that have made outstanding contributions to our ecosystem. If you think that your company deserves a spot here, reach out to office@ory.sh now!

Type	Name	Website
Adopter *	Raspberry PI Foundation	raspberrypi.org
Adopter *	Kyma Project	kyma-project.io
Adopter *	Tulip	tulip.com
Adopter *	Cashdeck / All My Funds	cashdeck.com.au
Adopter *	Hootsuite	hootsuite.com
Adopter *	Segment	segment.com
Adopter *	Arduino	arduino.cc
Adopter *	DataDetect	unifiedglobalarchiving.com/data-detect/
Adopter *	Sainsbury's	sainsburys.co.uk
Adopter *	Contraste	contraste.com
Adopter *	Reyah	reyah.eu
Adopter *	Zero	getzero.dev
Adopter *	Padis	padis.io
Adopter *	Cloudbear	cloudbear.eu
Adopter *	Security Onion Solutions	securityonionsolutions.com
Adopter *	Factly	factlylabs.com
Adopter *	Nortal	nortal.com
Adopter *	OrderMyGear	ordermygear.com
Adopter *	Spiri.bo	spiri.bo
Adopter *	Strivacity	strivacity.com
Adopter *	Hanko	hanko.io
Adopter *	Rabbit	rabbit.co.th
Adopter *	inMusic	inmusicbrands.com
Adopter *	Buhta	buhta.com
Adopter *	Connctd	connctd.com
Adopter *	Paralus	paralus.io
Adopter *	TIER IV	tier4.jp
Adopter *	R2Devops	r2devops.io
Adopter *	LunaSec	lunasec.io
Adopter *	Serlo	serlo.org
Adopter *	dyrector.io	dyrector.io
Adopter *	Stackspin	stackspin.net
Adopter *	Amplitude	amplitude.com
Adopter *	Pinniped	pinniped.dev
Adopter *	Pvotal	pvotal.tech

Many thanks to all individual contributors

* Uses one of Ory's major projects in production.

OAuth2 and OpenID Connect: Open Standards!

Ory Hydra implements Open Standards set by the IETF:

and the OpenID Foundation:

OpenID Connect Certified

Ory Hydra is an OpenID Foundation certified OpenID Provider (OP).

Ory Hydra is a certified OpenID Providier

The following OpenID profiles are certified:

Basic OpenID Provider (response types code)
Implicit OpenID Provider (response types id_token, id_token+token)
Hybrid OpenID Provider (response types code+id_token, code+id_token+token, code+token)
OpenID Provider Publishing Configuration Information
Dynamic OpenID Provider

To obtain certification, we deployed the reference user login and consent app (unmodified) and Ory Hydra v1.0.0.

Quickstart

This section is a starter guide to working with Ory Hydra. In-depth docs are available as well:

The documentation is available here.
The REST API documentation is available here.

Installation

Head over to the Ory Developer Documentation to learn how to install Ory Hydra on Linux, macOS, Windows, and Docker and how to build Ory Hydra from source.

Ecosystem

We build Ory on several guiding principles when it comes to our architecture design:

Minimal dependencies
Runs everywhere
Scales without effort
Minimize room for human and network errors

Ory's architecture is designed to run best on a Container Orchestration system such as Kubernetes, CloudFoundry, OpenShift, and similar projects. Binaries are small (5-15MB) and available for all popular processor types (ARM, AMD64, i386) and operating systems (FreeBSD, Linux, macOS, Windows) without system dependencies (Java, Node, Ruby, libxml, ...).

Ory Kratos: Identity and User Infrastructure and Management

Ory Kratos is an API-first Identity and User Management system that is built according to cloud architecture best practices. It implements core use cases that almost every software application needs to deal with: Self-service Login and Registration, Multi-Factor Authentication (MFA/2FA), Account Recovery and Verification, Profile, and Account Management.

Ory Hydra: OAuth2 & OpenID Connect Server

Ory Hydra is an OpenID Certifiedâ¢ OAuth2 and OpenID Connect Provider which easily connects to any existing identity system by writing a tiny "bridge" application. It gives absolute control over the user interface and user experience flows.

Ory Oathkeeper: Identity & Access Proxy

Ory Oathkeeper is a BeyondCorp/Zero Trust Identity & Access Proxy (IAP) with configurable authentication, authorization, and request mutation rules for your web services: Authenticate JWT, Access Tokens, API Keys, mTLS; Check if the contained subject is allowed to perform the request; Encode resulting content into custom headers (X-User-ID), JSON Web Tokens and more!

Ory Keto: Access Control Policies as a Server

Ory Keto is a policy decision point. It uses a set of access control policies, similar to AWS IAM Policies, in order to determine whether a subject (user, application, service, car, ...) is authorized to perform a certain action on a resource.

Security

Why should I use Ory Hydra? It's not that hard to implement two OAuth2 endpoints and there are numerous SDKs out there!

OAuth2 and OAuth2 related specifications are over 400 written pages. Implementing OAuth2 is easy, getting it right is hard. Ory Hydra is trusted by companies all around the world, has a vibrant community and faces millions of requests in production each day. Of course, we also compiled a security guide with more details on cryptography and security concepts. Read the security guide now.

Disclosing vulnerabilities

If you think you found a security vulnerability, please refrain from posting it publicly on the forums, the chat, or GitHub. You can find all info for responsible disclosure in our security.txt.

Benchmarks

Our continuous integration runs a collection of benchmarks against Ory Hydra. You can find the results here.

Telemetry

Our services collect summarized, anonymized data that can optionally be turned off. Click here to learn more.

Documentation

Guide

The full Ory Hydra documentation is available here.

HTTP API documentation

The HTTP API is documented here.

Upgrading and Changelog

New releases might introduce breaking changes. To help you identify and incorporate those changes, we document these changes in CHANGELOG.md.

Command line documentation

Run hydra -h or hydra help.

Develop

We love all contributions! Please read our contribution guidelines.

Dependencies

You need Go 1.13+ with GO111MODULE=on and (for the test suites):

Docker and Docker Compose
Makefile
NodeJS / npm

It is possible to develop Ory Hydra on Windows, but please be aware that all guides assume a Unix shell like bash or zsh.

Formatting Code

You can format all code using make format. Our CI checks if your code is properly formatted.

Running Tests

There are three types of tests you can run:

Short tests (do not require a SQL database like PostgreSQL)
Regular tests (do require PostgreSQL, MySQL, CockroachDB)
End to end tests (do require databases and will use a test browser)

All of the above tests can be run using the makefile. See the commands below.

Makefile commands

# quick tests
make quicktest

# regular tests
make test
test-resetdb

# end-to-end tests
make e2e

Short Tests

It is recommended to use the make file to run your tests using make quicktest , however, you can still use the go test command.

Please note:

All tests run against a sqlite in-memory database, thus it is required to use the -tags sqlite build tag.

Short tests run fairly quickly. You can either test all of the code at once:

go test -v -failfast -short -tags sqlite ./...

or test just a specific module:

go test -v -failfast -short -tags sqlite ./client

or a specific test:

go test -v -failfast -short -tags sqlite -run ^TestName$ ./...

Regular Tests

Regular tests require a database set up. Our test suite is able to work with docker directly (using ory/dockertest) but we encourage to use the Makefile instead. Using dockertest can bloat the number of Docker Images on your system and are quite slow. Instead we recommend doing:

make test

Please be aware that make test recreates the databases every time you run make test. This can be annoying if you are trying to fix something very specific and need the database tests all the time. In that case we suggest that you initialize the databases with:

make test-resetdb
export TEST_DATABASE_MYSQL='mysql://root:secret@(127.0.0.1:3444)/mysql?parseTime=true&multiStatements=true'
export TEST_DATABASE_POSTGRESQL='postgres://postgres:secret@127.0.0.1:3445/postgres?sslmode=disable'
export TEST_DATABASE_COCKROACHDB='cockroach://root@127.0.0.1:3446/defaultdb?sslmode=disable'

Then you can run go test as often as you'd like:

go test -p 1 ./...

# or in a module:
cd client; go test .

E2E Tests

The E2E tests use Cypress to run full browser tests. You can execute these tests with:

make e2e

The runner will not show the Browser window, as it runs in the CI Mode (background). That makes debugging these type of tests very difficult, but thankfully you can run the e2e test in the browser which helps with debugging! Just run:

./test/e2e/circle-ci.bash memory --watch

# Or for the JSON Web Token Access Token strategy:
# ./test/e2e/circle-ci.bash memory-jwt --watch

or if you would like to test one of the databases:

make test-resetdb
export TEST_DATABASE_MYSQL='mysql://root:secret@(127.0.0.1:3444)/mysql?parseTime=true&multiStatements=true'
export TEST_DATABASE_POSTGRESQL='postgres://postgres:secret@127.0.0.1:3445/postgres?sslmode=disable'
export TEST_DATABASE_COCKROACHDB='cockroach://root@127.0.0.1:3446/defaultdb?sslmode=disable'

# You can test against each individual database:
./test/e2e/circle-ci.bash postgres --watch
./test/e2e/circle-ci.bash memory --watch
./test/e2e/circle-ci.bash mysql --watch
# ...

Once you run the script, a Cypress window will appear. Hit the button "Run all Specs"!

The code for these tests is located in ./cypress/integration and ./cypress/support and ./cypress/helpers. The website you're seeing is located in ./test/e2e/oauth2-client.

OpenID Connect Conformity Tests

To run Ory Hydra against the OpenID Connect conformity suite, run

$ test/conformity/start.sh --build

and then in a separate shell

$ test/conformity/test.sh

Running these tests will take a significant amount of time which is why they are not part of the CI pipeline.

Build Docker

You can build a development Docker Image using:

make docker

Run the Docker Compose quickstarts

If you wish to check your code changes against any of the docker-compose quickstart files, run:

make docker
docker compose -f quickstart.yml up # ....

Add a new migration

mkdir persistence/sql/src/YYYYMMDD000001_migration_name/
Put the migration files into this directory, following the standard naming conventions. If you wish to execute different parts of a migration in separate transactions, add split marks (lines with the text --split) where desired. Why this might be necessary is explained in https://github.com/gobuffalo/fizz/issues/104.
Run make persistence/sql/migrations/<migration_id> to generate migration fragments.
If an update causes the migration to have fewer fragments than the number already generated, run make persistence/sql/migrations/<migration_id>-clean. This is equivalent to a rm command with the right parameters, but comes with better tab completion.
Before committing generated migration fragments, run the above clean command and generate a fresh copy of migration fragments to make sure the sql/src and sql/migrations directories are consistent.

Libraries and third-party projects

Official:

User Login & Consent Example

Community:

Visit this document for an overview of community projects and articles

Developer Blog:

Visit the Ory Blog for guides, tutorials and articles around Ory Hydra and the Ory ecosystem.

Top Related Projects

Convert designs to code with AI

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

Top Related Projects

Quick Overview

Pros

Cons

Code Examples

Getting Started

Competitor Comparisons

Pros of Keycloak

Cons of Keycloak

Code Comparison

Pros of oauth2-proxy

Cons of oauth2-proxy

Code Comparison

Pros of node-oidc-provider

Cons of node-oidc-provider

Code Comparison

Pros of Authelia

Cons of Authelia

Code Comparison

Pros of SuperTokens

Cons of SuperTokens

Code Comparison

Pros of Zitadel

Cons of Zitadel

Code Comparison

Convert designs to code with AI

README

Chat | Discussions | Newsletter Guide | API Docs | Code Docs Support this project! Work in Open Source, Ory is hiring!

Ory Hydra on the Ory Network

Ory Network Hybrid Support Plan

Get Started

OAuth 2.0 Client Credentials / Machine-to-Machine

OAuth 2.0 Authorize Code + OpenID Connect

What is Ory Hydra?

Who's using it?

OAuth2 and OpenID Connect: Open Standards!

OpenID Connect Certified

Quickstart

Installation

Ecosystem

Ory Kratos: Identity and User Infrastructure and Management

Ory Hydra: OAuth2 & OpenID Connect Server

Ory Oathkeeper: Identity & Access Proxy

Ory Keto: Access Control Policies as a Server

Security

Disclosing vulnerabilities

Benchmarks

Telemetry

Documentation

Guide

HTTP API documentation

Upgrading and Changelog

Command line documentation

Develop

Dependencies

Formatting Code

Running Tests

Short Tests

Regular Tests

E2E Tests

OpenID Connect Conformity Tests

Build Docker

Run the Docker Compose quickstarts

Add a new migration

Libraries and third-party projects

Top Related Projects

Convert designs to code with AI

Chat | Discussions | Newsletter

Guide | API Docs | Code Docs

Support this project!

Work in Open Source, Ory is hiring!