Community

Ory is possible because of a unique, experienced, and dedicated community. Sponsors, contributors, and adopters make this ecosystem possible and shape it in significant ways.

Important community resources include GitHub, Ory Slack Chat and GitHub Discussions for Ory Kratos, Ory Hydra, Ory Keto, Ory Oathkeeper and all other Ory projects, you can also visit our archived old forum.

Community Projects

Members of the Ory community have built technology, written blog posts, and published open source software that extends or modifies the core technology. This is not an exhaustive list. Want your own content here? Create a PR!

Please note that this content is not actively maintained by the Ory team, is written by the community and might be out of date, unmaintained, or otherwise faulty.

Ory Stack

• SSO and ACL example with Ory Stack in Kubernetes
• Starter for Svelte Kit and the Ory Stack
• Reference Ory Docker Compose Setup + Article
• WIP Ory Hydra/Kratos Integration in Go
• Ory Kratos "hydra-integration" branch
• Predefined dockertest libraries for Hydra, Kratos & Keto integration tests

Ory Kratos

• Ory Kratos Quarkus, Kotlin, and Qute example
• Ory Kratos Svelte Node self service
• Ory Kratos Sveltekit example
• Ory Kratos Next.js self service UI
• Ory Kratos Rescript React UI SPA + Bindings
• Styx: Ory Kratos/Hydra Erlang frontend UI

Ory Hydra

• Ory Hydra Identity Provider for over LDAP
• Ory Hydra Middleware for Gin (Go)
• Ory Hydra Two-factor authentication login provider
• Ory Hydra Identity Provider
• Ory Hydra PoC for OAuth 2.0/OIDC provider
• Ory Hydra Python login/consent provider example

Ory Keto

• KetoToDot Ory Keto relation tuples to dot notation converter

Work In Progress & Archived/Outdated

• WIP: Ory Kratos React example
• WIP: Ory Hydra for GCP
• WIP: Ory Hydra/ Ory Oathkeeper Zero Trust Reference "Hello World App"
• Golang login/consent provider and Ory stack example
• OpenID Connect client for Angular
• Archived: Ory Hydra Golang login/consent provider using Authboss user/password authentication

Community Articles & Tutorials

Ory Stack

• Open Source Authentication with Hydra and Kratos

Ory Kratos

• Building a Quarkus application with Ory Kratos
• How to write an application that integrates Kratos in Go
• Ory Kratos reverse proxy (Nginx) example

Ory Hydra

• Practical Example of Implementing OAuth 2.0 Using ory/hydra
• OAuth 2.0 with Ory Hydra and Vapor on iOS: Part 1, Part 2, Part 3, Part 4.
• Creating an OAuth 2.0 custom lambda authorizer for use with Amazons (AWS) API Gateway using Hydra
• Discussion on Access & Refresh Tokens

Ory Keto

• Looking at Zanzibar through Ory Keto

Ory Oathkeepeer

• User Managment using Ory Oathkeeper
• API Access Control with Ambassador and Ory Oathkeeper
• Ory Oathkeeper Istio best practices/reference configuration

Ory Dockertest

• Writing Tests for MongoDB using Dockertest in Go
• Integration tests in Golang with dockertest
• Go Package for better integration tests: Ory Dockertest
• Using Dockertest with Golang

Postman API Reference Collections

Note that while we try to keep the collections up to date, they might be outdated. Please open an issue if that is the case.

First, you have to install the Postman App for Windows, Mac, or Chrome. You can find it on the Postman Apps page.

Visit the Ory Postman Public Workspace and select the Collection you want to use and import it or select the Ory project you want to run below:

Our API Collections are built directly from the swagger specification (you can find it at the path /spec/api.json) and are organized into folders that categorize the various API calls.

For example, in the Ory Kratos collection, you will find all calls related to identities in the folder with the same name.

To be able to work with the collection you need to set the baseURl variable. For example, when running Ory Kratos as configured, the baseURl needs to be set to the public endpoint(in the Quickstart it ishttp://127.0.0.1:4433/).

You may also have to configure query parameters or the JSON method body, depending on the API call.

info

Do not store tokens in Postman as environment variables!
If you are signed in to the Postman application, it will automatically try to synchronize Collections and Environments with the Postman servers. This means that a token, which could allow someone else access to your APIs, is being uploaded to Postman's servers.
Postman has taken measures to ensure that tokens are encrypted and encourages users to store them in Environment Variables. Read more here.