Skip to content

Latest commit

 

History

History
236 lines (169 loc) · 13.1 KB

README.md

File metadata and controls

236 lines (169 loc) · 13.1 KB

Awesome Ory

An awesome list of the Ory ecosystem. Ory provides scalable, flexible, and secure identity and access management (IAM) solutions that empower developers to build innovative applications. Whether you handle billions of users or launch a startup, Ory makes security and compliance simple with open-source transparency and cutting-edge tools.

Docs Docs

If you have any questions or suggestions open a discussion, or join the Ory Chat!

See CONTRIBUTING.md for pointers on how to contribute.

Contents

Ecosystem

Overview of the main projects in the Ory ecosystem.

Developer resources

Developer resources and forums for discussing Ory and meeting other users

Blog posts

Ory blog guest articles

Are you building something with Ory?
Are you interested in Auth and security topics in general?
Do you want to share your knowledge and experience?
Reach out to get published in the Ory blog!

Ory ecosystem

Ory Kratos

Ory Hydra

Ory Keto

Ory Oathkeepeer

Ory Dockertest

Videos

Examples

Code examples that show how to integrate Ory with a framework, software stack, or how to solve a specific use case.

Ory Ecosystem

Ory Kratos

Ory Hydra

Projects

Community projects, configuration tools, or development helpers extending Ory services.

Ory Ecosystem

Ory Kratos

Ory Hydra

Ory Keto

Ory Oathkeeper

Ory Fosite

Services

Managed services that run Ory for you

Postman collections

The API Collections are built directly from the swagger specification (you can find it at the path /spec/api.json in GitHub) and are organized into folders that categorize the various API calls. To be able to work with the collection you need to set the baseURl variable. For example, when running Ory Kratos the baseURl needs to be set to the public endpoint. You may also have to configure query parameters or the JSON method body, depending on the API call.

Note that while the collections should be up to date, please open an issue here if that's not the case.

Don't 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.

Archived, Outdated, and WIP

Old, outdated, or incomplete projects - feel free to play around or revive them!