![\"ORY](\"./docs/images/banner_hydra.png\")
\n ![\"Build](\"https://circleci.com/gh/ory/hydra/tree/master.svg?style=shield\")
\n ![\"Coverage](\"https://coveralls.io/repos/ory/hydra/badge.svg?branch=master&service=github\"){kind=icon}
\n \n
\n
![](\"https://opencollective.com/ory/backers/badge.svg\"){kind=icon}
![](\"https://opencollective.com/ory/sponsors/badge.svg\"){kind=icon}
\n
| Type | \nName | \nLogo | \nWebsite | \n
|---|---|---|---|
| Sponsor | \nRaspberry PI Foundation | \n![\"Raspberry](\"./docs/adopters/raspi.svg\") | \n raspberrypi.org | \n
| Contributor | \nKyma Project\n | ![\"Kyma](\"./docs/adopters/kyma.svg\") | \n kyma-project.io | \n
| Sponsor | \nThoughtWorks | \n![\"ThoughtWorks\"](\"./docs/adopters/tw.svg\") | \n thoughtworks.com | \n
| Sponsor | \nTulip | \n![\"Tulip](\"./docs/adopters/tulip.svg\") | \n tulip.com | \n
| Sponsor | \nCashdeck / All My Funds | \n![\"All](\"./docs/adopters/allmyfunds.svg\") | \n cashdeck.com.au | \n
| Sponsor | \n3 Rein | \n![\"3REIN\"](\"./docs/adopters/3R-horiz.svg\") | \n 3rein.com (avaiable soon) | \n
| Contributor | \nHootsuite | \n![\"Hootsuite\"](\"./docs/adopters/hootsuite.svg\") | \n hootsuite.com | \n
| Adopter * | \nSegment | \n![\"Segment\"](\"./docs/adopters/segment.svg\") | \n segment.com | \n
| Adopter * | \nArduino | \n![\"Arduino\"](\"./docs/adopters/arduino.svg\") | \n arduino.cc | \n
![](\"https://opencollective.com/ory/contributors.svg?width=890&button=false\")
\n\nas well as all of our backers\n\n![](\"https://opencollective.com/ory/backers.svg?width=890\")
\n\nand past & current supporters (in alphabetical order) on [Patreon](https://www.patreon.com/_ory): Alexander Alimovs,\nBilly, Chancy Kennedy, Drozzy, Edwin Trejos, Howard Edidin, Ken Adler Oz Haven, Stefan Hans, TheCrealm.\n\n* Uses one of ORY's major projects in production.\n\n\n\n\n\n### OAuth2 and OpenID Connect: Open Standards!\n\nORY Hydra implements Open Standards set by the IETF:\n\n* [The OAuth 2.0 Authorization Framework](https://tools.ietf.org/html/rfc6749)\n* [OAuth 2.0 Threat Model and Security Considerations](https://tools.ietf.org/html/rfc6819)\n* [OAuth 2.0 Token Revocation](https://tools.ietf.org/html/rfc7009)\n* [OAuth 2.0 Token Introspection](https://tools.ietf.org/html/rfc7662)\n* [OAuth 2.0 for Native Apps](https://tools.ietf.org/html/draft-ietf-oauth-native-apps-10)\n* [Proof Key for Code Exchange by OAuth Public Clients](https://tools.ietf.org/html/rfc7636)\n\nand the OpenID Foundation:\n\n* [OpenID Connect Core 1.0](http://openid.net/specs/openid-connect-core-1_0.html)\n* [OpenID Connect Discovery 1.0](https://openid.net/specs/openid-connect-discovery-1_0.html)\n* [OpenID Connect Dynamic Client Registration 1.0](https://openid.net/specs/openid-connect-registration-1_0.html)\n* [OpenID Connect Front-Channel Logout 1.0](https://openid.net/specs/openid-connect-frontchannel-1_0.html)\n* [OpenID Connect Back-Channel Logout 1.0](https://openid.net/specs/openid-connect-backchannel-1_0.html)\n\n### OpenID Connect Certified\n\nORY Hydra is an OpenID Foundation [certified OpenID Provider (OP)](http://openid.net/certification/#OPs).\n\n\n ![\"ORY](\"./docs/images/oidc-cert.png\")
\n
![\"OAuth2](\"docs/images/oauth2-flow.gif\")
\n\n![\"ORY](\"docs/images/sec-console.png\")
\n\n\n### ORY Security Console: Administrative User Interface\n\nThe [ORY Security Console](https://console.ory.sh/) is a visual admin interface for managing ORY Hydra,\nORY Oathkeeper, and ORY Keto.\n\n### ORY Oathkeeper: Identity & Access Proxy\n\n[ORY Oathkeeper](https://github.com/ory/oathkeeper) is a BeyondCorp/Zero Trust Identity & Access Proxy (IAP) built\non top of OAuth2 and ORY Hydra.\n\n### ORY Keto: Access Control Policies as a Server\n\n[ORY Keto](https://github.com/ory/keto) is a policy decision point. It uses a set of access control policies, similar\nto AWS IAM Policies, in order to determine whether a subject (user, application, service, car, ...) is authorized to\nperform a certain action on a resource.\n\n### Examples\n\nThe [ory/examples](https://github.com/ory/examples) repository contains numerous examples of setting up this project\nindividually and together with other services from the ORY Ecosystem.\n\n## Security\n\n*Why should I use ORY Hydra? It's not that hard to implement two OAuth2 endpoints and there are numerous SDKs out there!*\n\nOAuth2 and OAuth2 related specifications are over 400 written pages. Implementing OAuth2 is easy, getting it right is hard.\nORY Hydra is trusted by companies all around the world, has a vibrant community and faces millions of requests in production\neach day. Of course, we also compiled a security guide with more details on cryptography and security concepts.\nRead [the security guide now](https://www.ory.sh/docs/next/hydra/security-architecture).\n\n### Disclosing vulnerabilities\n\nIf you think you found a security vulnerability, please refrain from posting it publicly on the forums, the chat, or GitHub\nand send us an email to [hi@ory.am](mailto:hi@ory.sh) instead.\n\n## Benchmarks\n\nOur continuous integration runs a collection of benchmarks against ORY Hydra. You can find the results [here](https://www.ory.sh/docs/next/performance/hydra).\n\n## Telemetry\n\nOur services collect summarized, anonymized data that can optionally be turned off. Click\n[here](https://www.ory.sh/docs/next/ecosystem/sqa) to learn more.\n\n## Documentation\n\n### Guide\n\nThe Guide is available [here](https://www.ory.sh/docs/next/hydra).\n\n### HTTP API documentation\n\nThe HTTP API is documented [here](https://www.ory.sh/docs/next/hydra/sdk/api).\n\n### Upgrading and Changelog\n\nNew releases might introduce breaking changes. To help you identify and incorporate those changes, we document these\nchanges in [UPGRADE.md](./UPGRADE.md) and [CHANGELOG.md](./CHANGELOG.md).\n\n### Command line documentation\n\nRun `hydra -h` or `hydra help`.\n\n### Develop\n\nDeveloping with ORY Hydra is as easy as:\n\n```\ngo get -d -u github.com/ory/hydra\ncd $GOPATH/src/github.com/ory/hydra\nmake init\nexport GO111MODULE=on\n## With database\nmake test\n## Without database\nmake quicktest\n```\n\nThen run it with in-memory database:\n\n```\nDSN=memory go run main.go serve all\n```\n\n**Notes**\n\n* We changed organization name from `ory-am` to `ory`. In order to keep backward compatibility, we did not rename Go packages.\n* You can ignore warnings similar to `package github.com/ory/hydra/cmd/server: case-insensitive import collision: \"github.com/sirupsen/logrus\" and \"github.com/sirupsen/logrus\"`.\n\n## Libraries and third-party projects\n\nOfficial:\n* [User Login & Consent Example](https://github.com/ory/hydra-login-consent-node)\n\nCommunity:\n* [Kubernetes helm chart](https://github.com/kubernetes/charts/pull/1022)\n* [Werther - an Identity Provider over LDAP](https://github.com/i-core/werther)\n\n:warning: Outdated Community Projects:\nThe following projects are outdated and won't work anymore in most cases. Having said that they still might help you to better understand how to integrate HYDRA and solve specific cases.\n* [ORY Hydra middleware for Gin](https://github.com/janekolszak/gin-hydra)\n* [Consent App SDK for Go](https://github.com/janekolszak/idp)\n\n## Blog posts & articles\n\n* [Creating an oauth2 custom lamda authorizer for use with Amazons (AWS) API Gateway using Hydra](https://blogs.edwardwilde.com/2017/01/12/creating-an-oauth2-custom-lamda-authorizer-for-use-with-amazons-aws-api-gateway-using-hydra/)\n* Warning, ORY Hydra has changed almost everything since writing this\narticle: [Hydra: Run your own Identity and Access Management service in <5 Minutes](https://blog.gopheracademy.com/advent-2015/hydra-auth/)\n","readmeFilename":"README.md"}