├── .bin ├── license-engine.sh ├── licenses └── list-licenses ├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE │ ├── BUG-REPORT.yml │ ├── DESIGN-DOC.yml │ ├── FEATURE-REQUEST.yml │ └── config.yml ├── auto_assign.yml ├── config.yml ├── pull_request_template.md └── workflows │ ├── closed_references.yml │ ├── conventional_commits.yml │ ├── labels.yml │ ├── licenses.yml │ └── stale.yml ├── .reference-ignore ├── .reports └── dep-licenses.csv ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── Ory_Summit_21_Day_1_-_Andrew_Minkin_-__Using_Kratos_and_Keto_in_production_.pdf ├── Ory_Summit_21_Day_1_-_Ashley_Manraj_-_Customizing_Ory_Keto_with_global_scale_data_sharing_requirements.pdf ├── Ory_Summit_21_Day_1_-_Bill_Monkman_-_Zero_Bootstrapping_SaaS_applications_leveraging_Ory_Kratos_and_Oathkeeper.pdf ├── Ory_Summit_21_Day_1_-_Christian_Roggia_-_Building_a_Google-like_IAM_system_from_scratch_through_Ory_products.pdf ├── Ory_Summit_21_Day_1_-_Dimitrij_Drus_-_Davids_Slingshot_-_Leveraging_Ory.pdf ├── Ory_Summit_21_Day_1_-_Keynote_-_Future_Directions_for_the_New_ID_Stack.pdf ├── Ory_Summit_21_Day_1_-_Sashi_Deshetti_Kavach_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf ├── Ory_Summit_21_Day_2_-_Akibur_Rahman_-_Implementing_the_Ory_stack_at_Padis.pdf ├── Ory_Summit_21_Day_2_-_Amorevino_-_Ory-Cloud_Service_for_App_Developers.pdf ├── Ory_Summit_21_Day_2_-_David_Alexander_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf ├── Ory_Summit_21_Day_2_-_Dirk_Riehle_-_Open_Source_License_Compliance_and_Ory_Open_Source.pdf ├── Ory_Summit_21_Day_2_-_Jakob_Sinclair_-_Building_a_community_management_infrastructure_with_Ory_open_source_software.pdf ├── Ory_Summit_21_Day_2_-_Keynote_-_Ory_Cloud_Technical_Direction.pdf ├── Ory_Summit_21_Day_2_-_Stepan_Rakitin_-_SumUp_Self-service_OIDC_for_with_Ory_Hydra_and_Terraform.pdf ├── Ory_Summit_22_-_Aeneas_Rekkas_Klaus_Herrman_-_Introducing_the_Ory_Network.pdf ├── Ory_Summit_22_-_Amorevino_-_Delightful_auth_experience_for_social_e-commerce_apps.pdf ├── Ory_Summit_22_-_Artur_Balsam_-_Threat_Modelling_101.pdf ├── Ory_Summit_22_-_Bobur_Umurzokov_-_Centralized Authentication with Apache APISIX and Ory.pdf ├── Ory_Summit_22_-_Deniz_Onur_Duzgun_-_Make_Auth_Great_Again_With_Ory.pdf ├── Ory_Summit_22_-_Harri_Hursti_-_Zero_Trust_Now_we_must_but_what_it_means.pdf ├── Ory_Summit_22_-_Ilya_Migal_Dominik_Lekse_-_One_auth_gateway_to_authenticate_them_all.pdf ├── Ory_Summit_22_-_Lloyd_W_Taylor_-_Building_applications_in_the_cloud.pdf ├── Ory_Summit_22_-_Lukasz_Harasimowicz_-_Running_Ory_on_30M_user_platform.pdf ├── Ory_Summit_22_-_Mal_Curtis_Ory_in_the_inMusic_cloud.pdf ├── Ory_Summit_22_-_Patrick_Neu_Henning_Perl_-_Making_of_the_Ory_Permission_Language.pdf ├── Ory_Summit_22_-_Shota_Sawada_-_Replaceing_Identity_Server_with_Ory.pdf ├── Ory_Summit_22_-_Thomas_Curran_-_Securing_the_digital_world.pdf ├── Ory_Summit_22_-_Xavier_Vello_-_Designing_OSS_project_for_low_maintenance.pdf ├── README.md ├── SECURITY.md ├── img ├── 2022-spotlight-banner-989x400.png ├── banner-1280x400.png ├── logo-300x300.png ├── small-banner-385x250.png └── spotlight-banner-1920x400.png └── wallpaper ├── abstract ├── ory-wallpaper-abstract-1-dark.png ├── ory-wallpaper-abstract-1.png ├── ory-wallpaper-abstract-2-dark.png ├── ory-wallpaper-abstract-2.png ├── ory-wallpaper-abstract-3-dark.png └── ory-wallpaper-abstract-3.png ├── ory-digital-mountain-1920x1200.png ├── ory-digital-mountain-2880x1800.png ├── ory-summit-1920x1200.png ├── ory-summit-2880x1800.png ├── ory-wallpaper-2022-2560x1440.png └── ory-wallpaper-wide.jpg /.bin/license-engine.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # This script detects non-compliant licenses in the output of language-specific license checkers. 4 | 5 | # These licenses are allowed. 6 | # These are the exact and complete license strings for 100% legal certainty, no regexes. 7 | ALLOWED_LICENSES=( 8 | '0BSD' 9 | 'AFLv2.1' 10 | 'AFLv2.1,BSD' 11 | '(AFL-2.1 OR BSD-3-Clause)' 12 | 'Apache 2.0' 13 | 'Apache-2.0' 14 | '(Apache-2.0 OR MPL-1.1)' 15 | 'Apache-2.0 AND MIT' 16 | 'Apache License, Version 2.0' 17 | 'Apache*' 18 | 'Artistic-2.0' 19 | 'BlueOak-1.0.0' 20 | 'BSD' 21 | 'BSD*' 22 | 'BSD-2-Clause' 23 | '(BSD-2-Clause OR MIT OR Apache-2.0)' 24 | 'BSD-3-Clause' 25 | '(BSD-3-Clause OR GPL-2.0)' 26 | 'BSD-3-Clause OR MIT' 27 | '(BSD-3-Clause AND Apache-2.0)' 28 | 'CC0-1.0' 29 | 'CC-BY-3.0' 30 | 'CC-BY-4.0' 31 | '(CC-BY-4.0 AND MIT)' 32 | 'ISC' 33 | 'ISC*' 34 | 'LGPL-2.1' # LGPL allows commercial use, requires only that modifications to LGPL-protected libraries are published under a GPL-compatible license 35 | 'MIT' 36 | 'MIT*' 37 | 'MIT-0' 38 | 'MIT AND ISC' 39 | '(MIT AND BSD-3-Clause)' 40 | '(MIT AND Zlib)' 41 | '(MIT OR Apache-2.0)' 42 | '(MIT OR CC0-1.0)' 43 | '(MIT OR GPL-2.0)' 44 | 'MPL-2.0' 45 | '(MPL-2.0 OR Apache-2.0)' 46 | 'Public Domain' 47 | 'Python-2.0' # the Python-2.0 is a permissive license, see https://en.wikipedia.org/wiki/Python_License 48 | 'Unlicense' 49 | 'WTFPL' 50 | 'WTFPL OR ISC' 51 | '(WTFPL OR MIT)' 52 | '(MIT OR WTFPL)' 53 | 'LGPL-3.0-or-later' # Requires only that modifications to LGPL-protected libraries are published under a GPL-compatible license which is not the case at Ory 54 | ) 55 | 56 | # These modules don't work with the current license checkers 57 | # and have been manually verified to have a compatible license (regex format). 58 | APPROVED_MODULES=( 59 | 'https://github.com/ory-corp/cloud/' # Ory IP 60 | 'github.com/ory/hydra-client-go' # Apache-2.0 61 | 'github.com/ory/hydra-client-go/v2' # Apache-2.0 62 | 'github.com/ory/kratos-client-go' # Apache-2.0 63 | 'github.com/gobuffalo/github_flavored_markdown' # MIT 64 | 'buffers@0.1.1' # MIT: original source at http://github.com/substack/node-bufferlist is deleted but a fork at https://github.com/pkrumins/node-bufferlist/blob/master/LICENSE contains the original license by the original author (James Halliday) 65 | 'https://github.com/iconify/iconify/packages/react' # MIT: license is in root of monorepo at https://github.com/iconify/iconify/blob/main/license.txt 66 | 'github.com/gobuffalo/.*' # MIT: license is in root of monorepo at https://github.com/gobuffalo/github_flavored_markdown/blob/main/LICENSE 67 | 'github.com/ory-corp/cloud/.*' # Ory IP 68 | 'github.com/golang/freetype/.*' # FreeType license: https://freetype.sourceforge.net/FTL.TXT 69 | 'go.opentelemetry.io/otel/exporters/jaeger/internal/third_party/thrift/lib/go/thrift' # Incorrect detection, actually Apache-2.0: https://github.com/open-telemetry/opentelemetry-go/blob/exporters/jaeger/v1.17.0/exporters/jaeger/internal/third_party/thrift/LICENSE 70 | 'go.uber.org/zap/exp/.*' # MIT license is in root of exp folder in monorepo at https://github.com/uber-go/zap/blob/master/exp/LICENSE 71 | 'github.com/ory/client-go' # Apache-2.0 72 | 'github.com/ian-kent/linkio' # BSD - https://github.com/ian-kent/linkio/blob/97566b8728870dac1c9863ba5b0f237c39166879/linkio.go#L1-L3 73 | 'github.com/t-k/fluent-logger-golang/fluent' # Apache-2.0 https://github.com/t-k/fluent-logger-golang/blob/master/LICENSE 74 | 'github.com/jmespath/go-jmespath' # Apache-2.0 https://github.com/jmespath/go-jmespath/blob/master/LICENSE 75 | 'github.com/ory/keto/proto/ory/keto/opl/v1alpha1' # Apache-2.0 - submodule of keto 76 | 'github.com/ory/keto/proto/ory/keto/relation_tuples/v1alpha2' # Apache-2.0 - submodule of keto 77 | '@ory-corp/.*' # Ory IP 78 | 'github.com/apache/arrow/.*' # Apache-2.0 https://github.com/apache/arrow/blob/main/LICENSE.txt 79 | 'github.com/ory-corp/webhook-target' # Ory IP 80 | '@ory/keto-grpc-client.*' # Apache-2.0 - submodule of keto 81 | 'golden-fleece@1.0.9' # MIT: https://github.com/Rich-Harris/golden-fleece/blob/master/LICENSE 82 | 'github.com/gogo/googleapis/.*' # Apache-2.0 https://github.com/gogo/googleapis/blob/master/LICENSE 83 | ) 84 | 85 | # These lines in the output should be ignored (plain text, no regex). 86 | IGNORE_LINES=( 87 | '"module name","licenses"' # header of license output for Node.js 88 | ) 89 | 90 | echo_green() { 91 | printf "\e[1;92m%s\e[0m\n" "$@" 92 | } 93 | 94 | echo_red() { 95 | printf "\e[0;91m%s\e[0m\n" "$@" 96 | } 97 | 98 | # capture STDIN 99 | input=$(cat -) 100 | 101 | # remove ignored lines 102 | for ignored in "${IGNORE_LINES[@]}"; do 103 | input=$(echo "$input" | grep -vF "$ignored") 104 | done 105 | 106 | # remove pre-approved modules 107 | for approved in "${APPROVED_MODULES[@]}"; do 108 | input=$(echo "$input" | grep -vE "\"${approved}\"") 109 | input=$(echo "$input" | grep -vE "\"Custom: ${approved}\"") 110 | done 111 | 112 | # remove allowed licenses 113 | for allowed in "${ALLOWED_LICENSES[@]}"; do 114 | input=$(echo "$input" | grep -vF "\"${allowed}\"") 115 | done 116 | 117 | # anything left in the input at this point is a module with an invalid license 118 | 119 | # print outcome 120 | if [ -z "$input" ]; then 121 | echo_green "Licenses are okay." 122 | else 123 | echo_red "Unknown licenses found!" 124 | echo "$input" 125 | exit 1 126 | fi 127 | -------------------------------------------------------------------------------- /.bin/licenses: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | set -e 3 | 4 | # Get the directory where this script is located 5 | bin_dir="$(cd "$(dirname "$0")" && pwd)" 6 | 7 | { echo "Checking licenses ..."; } 2>/dev/null 8 | "${bin_dir}/list-licenses" | "${bin_dir}/license-engine.sh" 9 | -------------------------------------------------------------------------------- /.bin/list-licenses: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | set -e 3 | 4 | bin_dir="$(cd "$(dirname "$0")" && pwd)" 5 | 6 | # list Node licenses 7 | if [ -f package.json ]; then 8 | if jq -e '.dependencies and (.dependencies | keys | length > 0)' package.json >/dev/null; then 9 | npx --yes license-checker --production --csv --excludePrivatePackages --customPath "${bin_dir}"/license-template-node.json | grep -v '^$' 10 | echo 11 | else 12 | echo "No dependencies found in package.json" >&2 13 | echo 14 | fi 15 | fi 16 | 17 | # list Go licenses 18 | if [ -f go.mod ]; then 19 | # List all direct Go module dependencies, transform their paths to root module paths 20 | # (e.g., github.com/ory/x instead of github.com/ory/x/foo/bar), and generate a license report 21 | # for each unique root module. This ensures that the license report is generated for the root 22 | # module of a repository, where licenses are typically defined. 23 | go_modules=$( 24 | go list -f "{{if not .Indirect}}{{.Path}}{{end}}" -m ... | 25 | sort -u | 26 | awk -F/ '{ if ($1 == "github.com" && NF >= 3) { print $1"/"$2"/"$3 } else { print } }' | 27 | sort -u 28 | ) 29 | if [ -z "$go_modules" ]; then 30 | echo "No Go modules found" >&2 31 | else 32 | # Workaround until https://github.com/google/go-licenses/issues/307 is fixed 33 | # .bin/go-licenses report "$module_name" --template .bin/license-template-go.tpl 2>/dev/null 34 | # 35 | echo "$go_modules" | xargs -I {} sh -c '.bin/go-licenses report --template .bin/license-template-go.tpl {}' | grep -v '^$' 36 | echo 37 | fi 38 | fi 39 | -------------------------------------------------------------------------------- /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/FUNDING.yml 3 | 4 | # These are supported funding model platforms 5 | 6 | # github: 7 | patreon: _ory 8 | open_collective: ory 9 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/BUG-REPORT.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/ISSUE_TEMPLATE/BUG-REPORT.yml 3 | 4 | description: "Create a bug report" 5 | labels: 6 | - bug 7 | name: "Bug Report" 8 | body: 9 | - attributes: 10 | value: "Thank you for taking the time to fill out this bug report!\n" 11 | type: markdown 12 | - attributes: 13 | label: "Preflight checklist" 14 | options: 15 | - label: 16 | "I could not find a solution in the existing issues, docs, nor 17 | discussions." 18 | required: true 19 | - label: 20 | "I agree to follow this project's [Code of 21 | Conduct](https://github.com/ory/summit/blob/master/CODE_OF_CONDUCT.md)." 22 | required: true 23 | - label: 24 | "I have read and am following this repository's [Contribution 25 | Guidelines](https://github.com/ory/summit/blob/master/CONTRIBUTING.md)." 26 | required: true 27 | - label: 28 | "I have joined the [Ory Community Slack](https://slack.ory.sh)." 29 | - label: 30 | "I am signed up to the [Ory Security Patch 31 | Newsletter](https://www.ory.sh/l/sign-up-newsletter)." 32 | id: checklist 33 | type: checkboxes 34 | - attributes: 35 | description: 36 | "Enter the slug or API URL of the affected Ory Network project. Leave 37 | empty when you are self-hosting." 38 | label: "Ory Network Project" 39 | placeholder: "https://.projects.oryapis.com" 40 | id: ory-network-project 41 | type: input 42 | - attributes: 43 | description: "A clear and concise description of what the bug is." 44 | label: "Describe the bug" 45 | placeholder: "Tell us what you see!" 46 | id: describe-bug 47 | type: textarea 48 | validations: 49 | required: true 50 | - attributes: 51 | description: | 52 | Clear, formatted, and easy to follow steps to reproduce the behavior: 53 | placeholder: | 54 | Steps to reproduce the behavior: 55 | 56 | 1. Run `docker run ....` 57 | 2. Make API Request to with `curl ...` 58 | 3. Request fails with response: `{"some": "error"}` 59 | label: "Reproducing the bug" 60 | id: reproduce-bug 61 | type: textarea 62 | validations: 63 | required: true 64 | - attributes: 65 | description: 66 | "Please copy and paste any relevant log output. This will be 67 | automatically formatted into code, so no need for backticks. Please 68 | redact any sensitive information" 69 | label: "Relevant log output" 70 | render: shell 71 | placeholder: | 72 | log=error .... 73 | id: logs 74 | type: textarea 75 | - attributes: 76 | description: 77 | "Please copy and paste any relevant configuration. This will be 78 | automatically formatted into code, so no need for backticks. Please 79 | redact any sensitive information!" 80 | label: "Relevant configuration" 81 | render: yml 82 | placeholder: | 83 | server: 84 | admin: 85 | port: 1234 86 | id: config 87 | type: textarea 88 | - attributes: 89 | description: "What version of our software are you running?" 90 | label: Version 91 | id: version 92 | type: input 93 | validations: 94 | required: true 95 | - attributes: 96 | label: "On which operating system are you observing this issue?" 97 | options: 98 | - Ory Network 99 | - macOS 100 | - Linux 101 | - Windows 102 | - FreeBSD 103 | - Other 104 | id: operating-system 105 | type: dropdown 106 | - attributes: 107 | label: "In which environment are you deploying?" 108 | options: 109 | - Ory Network 110 | - Docker 111 | - "Docker Compose" 112 | - "Kubernetes with Helm" 113 | - Kubernetes 114 | - Binary 115 | - Other 116 | id: deployment 117 | type: dropdown 118 | - attributes: 119 | description: "Add any other context about the problem here." 120 | label: Additional Context 121 | id: additional 122 | type: textarea 123 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/DESIGN-DOC.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/ISSUE_TEMPLATE/DESIGN-DOC.yml 3 | 4 | description: 5 | "A design document is needed for non-trivial changes to the code base." 6 | labels: 7 | - rfc 8 | name: "Design Document" 9 | body: 10 | - attributes: 11 | value: | 12 | Thank you for writing this design document. 13 | 14 | One of the key elements of Ory's software engineering culture is the use of defining software designs through design docs. These are relatively informal documents that the primary author or authors of a software system or application create before they embark on the coding project. The design doc documents the high level implementation strategy and key design decisions with emphasis on the trade-offs that were considered during those decisions. 15 | 16 | Ory is leaning heavily on [Google's design docs process](https://www.industrialempathy.com/posts/design-docs-at-google/) 17 | and [Golang Proposals](https://github.com/golang/proposal). 18 | 19 | Writing a design doc before contributing your change ensures that your ideas are checked with 20 | the community and maintainers. It will save you a lot of time developing things that might need to be changed 21 | after code reviews, and your pull requests will be merged faster. 22 | type: markdown 23 | - attributes: 24 | label: "Preflight checklist" 25 | options: 26 | - label: 27 | "I could not find a solution in the existing issues, docs, nor 28 | discussions." 29 | required: true 30 | - label: 31 | "I agree to follow this project's [Code of 32 | Conduct](https://github.com/ory/summit/blob/master/CODE_OF_CONDUCT.md)." 33 | required: true 34 | - label: 35 | "I have read and am following this repository's [Contribution 36 | Guidelines](https://github.com/ory/summit/blob/master/CONTRIBUTING.md)." 37 | required: true 38 | - label: 39 | "I have joined the [Ory Community Slack](https://slack.ory.sh)." 40 | - label: 41 | "I am signed up to the [Ory Security Patch 42 | Newsletter](https://www.ory.sh/l/sign-up-newsletter)." 43 | id: checklist 44 | type: checkboxes 45 | - attributes: 46 | description: 47 | "Enter the slug or API URL of the affected Ory Network project. Leave 48 | empty when you are self-hosting." 49 | label: "Ory Network Project" 50 | placeholder: "https://.projects.oryapis.com" 51 | id: ory-network-project 52 | type: input 53 | - attributes: 54 | description: | 55 | This section gives the reader a very rough overview of the landscape in which the new system is being built and what is actually being built. This isn’t a requirements doc. Keep it succinct! The goal is that readers are brought up to speed but some previous knowledge can be assumed and detailed info can be linked to. This section should be entirely focused on objective background facts. 56 | label: "Context and scope" 57 | id: scope 58 | type: textarea 59 | validations: 60 | required: true 61 | 62 | - attributes: 63 | description: | 64 | A short list of bullet points of what the goals of the system are, and, sometimes more importantly, what non-goals are. Note, that non-goals aren’t negated goals like “The system shouldn’t crash”, but rather things that could reasonably be goals, but are explicitly chosen not to be goals. A good example would be “ACID compliance”; when designing a database, you’d certainly want to know whether that is a goal or non-goal. And if it is a non-goal you might still select a solution that provides it, if it doesn’t introduce trade-offs that prevent achieving the goals. 65 | label: "Goals and non-goals" 66 | id: goals 67 | type: textarea 68 | validations: 69 | required: true 70 | 71 | - attributes: 72 | description: | 73 | This section should start with an overview and then go into details. 74 | The design doc is the place to write down the trade-offs you made in designing your software. Focus on those trade-offs to produce a useful document with long-term value. That is, given the context (facts), goals and non-goals (requirements), the design doc is the place to suggest solutions and show why a particular solution best satisfies those goals. 75 | 76 | The point of writing a document over a more formal medium is to provide the flexibility to express the problem at hand in an appropriate manner. Because of this, there is no explicit guidance on how to actually describe the design. 77 | label: "The design" 78 | id: design 79 | type: textarea 80 | validations: 81 | required: true 82 | 83 | - attributes: 84 | description: | 85 | If the system under design exposes an API, then sketching out that API is usually a good idea. In most cases, however, one should withstand the temptation to copy-paste formal interface or data definitions into the doc as these are often verbose, contain unnecessary detail and quickly get out of date. Instead, focus on the parts that are relevant to the design and its trade-offs. 86 | label: "APIs" 87 | id: apis 88 | type: textarea 89 | 90 | - attributes: 91 | description: | 92 | Systems that store data should likely discuss how and in what rough form this happens. Similar to the advice on APIs, and for the same reasons, copy-pasting complete schema definitions should be avoided. Instead, focus on the parts that are relevant to the design and its trade-offs. 93 | label: "Data storage" 94 | id: persistence 95 | type: textarea 96 | 97 | - attributes: 98 | description: | 99 | Design docs should rarely contain code, or pseudo-code except in situations where novel algorithms are described. As appropriate, link to prototypes that show the feasibility of the design. 100 | label: "Code and pseudo-code" 101 | id: pseudocode 102 | type: textarea 103 | 104 | - attributes: 105 | description: | 106 | One of the primary factors that would influence the shape of a software design and hence the design doc, is the degree of constraint of the solution space. 107 | 108 | On one end of the extreme is the “greenfield software project”, where all we know are the goals, and the solution can be whatever makes the most sense. Such a document may be wide-ranging, but it also needs to quickly define a set of rules that allow zooming in on a manageable set of solutions. 109 | 110 | On the other end are systems where the possible solutions are very well defined, but it isn't at all obvious how they could even be combined to achieve the goals. This may be a legacy system that is difficult to change and wasn't designed to do what you want it to do or a library design that needs to operate within the constraints of the host programming language. 111 | 112 | In this situation, you may be able to enumerate all the things you can do relatively easily, but you need to creatively put those things together to achieve the goals. There may be multiple solutions, and none of them are great, and hence such a document should focus on selecting the best way given all identified trade-offs. 113 | label: "Degree of constraint" 114 | id: constrait 115 | type: textarea 116 | 117 | - attributes: 118 | description: | 119 | This section lists alternative designs that would have reasonably achieved similar outcomes. The focus should be on the trade-offs that each respective design makes and how those trade-offs led to the decision to select the design that is the primary topic of the document. 120 | 121 | While it is fine to be succinct about a solution that ended up not being selected, this section is one of the most important ones as it shows very explicitly why the selected solution is the best given the project goals and how other solutions, that the reader may be wondering about, introduce trade-offs that are less desirable given the goals. 122 | 123 | label: Alternatives considered 124 | id: alternatives 125 | type: textarea 126 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml 3 | 4 | description: 5 | "Suggest an idea for this project without a plan for implementation" 6 | labels: 7 | - feat 8 | name: "Feature Request" 9 | body: 10 | - attributes: 11 | value: | 12 | Thank you for suggesting an idea for this project! 13 | 14 | If you already have a plan to implement a feature or a change, please create a [design document](https://github.com/aeneasr/gh-template-test/issues/new?assignees=&labels=rfc&template=DESIGN-DOC.yml) instead if the change is non-trivial! 15 | type: markdown 16 | - attributes: 17 | label: "Preflight checklist" 18 | options: 19 | - label: 20 | "I could not find a solution in the existing issues, docs, nor 21 | discussions." 22 | required: true 23 | - label: 24 | "I agree to follow this project's [Code of 25 | Conduct](https://github.com/ory/summit/blob/master/CODE_OF_CONDUCT.md)." 26 | required: true 27 | - label: 28 | "I have read and am following this repository's [Contribution 29 | Guidelines](https://github.com/ory/summit/blob/master/CONTRIBUTING.md)." 30 | required: true 31 | - label: 32 | "I have joined the [Ory Community Slack](https://slack.ory.sh)." 33 | - label: 34 | "I am signed up to the [Ory Security Patch 35 | Newsletter](https://www.ory.sh/l/sign-up-newsletter)." 36 | id: checklist 37 | type: checkboxes 38 | - attributes: 39 | description: 40 | "Enter the slug or API URL of the affected Ory Network project. Leave 41 | empty when you are self-hosting." 42 | label: "Ory Network Project" 43 | placeholder: "https://.projects.oryapis.com" 44 | id: ory-network-project 45 | type: input 46 | - attributes: 47 | description: 48 | "Is your feature request related to a problem? Please describe." 49 | label: "Describe your problem" 50 | placeholder: 51 | "A clear and concise description of what the problem is. Ex. I'm always 52 | frustrated when [...]" 53 | id: problem 54 | type: textarea 55 | validations: 56 | required: true 57 | - attributes: 58 | description: | 59 | Describe the solution you'd like 60 | placeholder: | 61 | A clear and concise description of what you want to happen. 62 | label: "Describe your ideal solution" 63 | id: solution 64 | type: textarea 65 | validations: 66 | required: true 67 | - attributes: 68 | description: "Describe alternatives you've considered" 69 | label: "Workarounds or alternatives" 70 | id: alternatives 71 | type: textarea 72 | validations: 73 | required: true 74 | - attributes: 75 | description: "What version of our software are you running?" 76 | label: Version 77 | id: version 78 | type: input 79 | validations: 80 | required: true 81 | - attributes: 82 | description: 83 | "Add any other context or screenshots about the feature request here." 84 | label: Additional Context 85 | id: additional 86 | type: textarea 87 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/ISSUE_TEMPLATE/config.yml 3 | 4 | blank_issues_enabled: false 5 | contact_links: 6 | - name: Ory summit Forum 7 | url: https://github.com/orgs/ory/discussions 8 | about: 9 | Please ask and answer questions here, show your implementations and 10 | discuss ideas. 11 | - name: Ory Chat 12 | url: https://www.ory.sh/chat 13 | about: 14 | Hang out with other Ory community members to ask and answer questions. 15 | -------------------------------------------------------------------------------- /.github/auto_assign.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/auto_assign.yml 3 | 4 | # Set to true to add reviewers to pull requests 5 | addReviewers: true 6 | 7 | # Set to true to add assignees to pull requests 8 | addAssignees: true 9 | 10 | # A list of reviewers to be added to pull requests (GitHub user name) 11 | assignees: 12 | - ory/maintainers 13 | 14 | # A number of reviewers added to the pull request 15 | # Set 0 to add all the reviewers (default: 0) 16 | numberOfReviewers: 0 17 | -------------------------------------------------------------------------------- /.github/config.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/config.yml 3 | 4 | todo: 5 | keyword: "@todo" 6 | label: todo 7 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | 12 | 13 | ## Related Issue or Design Document 14 | 15 | 29 | 30 | ## Checklist 31 | 32 | 36 | 37 | - [ ] I have read the [contributing guidelines](../blob/master/CONTRIBUTING.md) and signed the CLA. 38 | - [ ] I have referenced an issue containing the design document if my change introduces a new feature. 39 | - [ ] I have read the [security policy](../security/policy). 40 | - [ ] I confirm that this pull request does not address a security vulnerability. 41 | If this pull request addresses a security vulnerability, 42 | I confirm that I got approval (please contact [security@ory.sh](mailto:security@ory.sh)) from the maintainers to push the changes. 43 | - [ ] I have added tests that prove my fix is effective or that my feature works. 44 | - [ ] I have added the necessary documentation within the code base (if appropriate). 45 | 46 | ## Further comments 47 | 48 | 52 | -------------------------------------------------------------------------------- /.github/workflows/closed_references.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/workflows/closed_references.yml 3 | 4 | name: Closed Reference Notifier 5 | 6 | on: 7 | schedule: 8 | - cron: "0 0 * * *" 9 | workflow_dispatch: 10 | inputs: 11 | issueLimit: 12 | description: Max. number of issues to create 13 | required: true 14 | default: "5" 15 | 16 | jobs: 17 | find_closed_references: 18 | if: github.repository_owner == 'ory' 19 | runs-on: ubuntu-latest 20 | name: Find closed references 21 | steps: 22 | - uses: actions/checkout@v2 23 | - uses: actions/setup-node@v2-beta 24 | with: 25 | node-version: "14" 26 | - uses: ory/closed-reference-notifier@v1 27 | with: 28 | token: ${{ secrets.GITHUB_TOKEN }} 29 | issueLabels: upstream,good first issue,help wanted 30 | issueLimit: ${{ github.event.inputs.issueLimit || '5' }} 31 | -------------------------------------------------------------------------------- /.github/workflows/conventional_commits.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/workflows/conventional_commits.yml 3 | 4 | name: Conventional commits 5 | 6 | # This GitHub CI Action enforces that pull request titles follow conventional commits. 7 | # More info at https://www.conventionalcommits.org. 8 | # 9 | # The Ory-wide defaults for commit titles and scopes are below. 10 | # Your repository can add/replace elements via a configuration file at the path below. 11 | # More info at https://github.com/ory/ci/blob/master/conventional_commit_config/README.md 12 | 13 | on: 14 | pull_request_target: 15 | types: 16 | - edited 17 | - opened 18 | - ready_for_review 19 | - reopened 20 | # pull_request: # for debugging, uses config in local branch but supports only Pull Requests from this repo 21 | 22 | jobs: 23 | main: 24 | name: Validate PR title 25 | runs-on: ubuntu-latest 26 | steps: 27 | - uses: actions/checkout@v3 28 | - id: config 29 | uses: ory/ci/conventional_commit_config@master 30 | with: 31 | config_path: .github/conventional_commits.json 32 | default_types: | 33 | feat 34 | fix 35 | revert 36 | docs 37 | style 38 | refactor 39 | test 40 | build 41 | autogen 42 | security 43 | ci 44 | chore 45 | default_scopes: | 46 | deps 47 | docs 48 | default_require_scope: false 49 | - uses: amannn/action-semantic-pull-request@v4 50 | env: 51 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 52 | with: 53 | types: ${{ steps.config.outputs.types }} 54 | scopes: ${{ steps.config.outputs.scopes }} 55 | requireScope: ${{ steps.config.outputs.requireScope }} 56 | subjectPattern: ^(?![A-Z]).+$ 57 | subjectPatternError: | 58 | The subject should start with a lowercase letter, yours is uppercase: 59 | "{subject}" 60 | -------------------------------------------------------------------------------- /.github/workflows/labels.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/workflows/labels.yml 3 | 4 | name: Synchronize Issue Labels 5 | 6 | on: 7 | workflow_dispatch: 8 | push: 9 | branches: 10 | - master 11 | 12 | jobs: 13 | milestone: 14 | if: github.repository_owner == 'ory' 15 | name: Synchronize Issue Labels 16 | runs-on: ubuntu-latest 17 | steps: 18 | - name: Checkout 19 | uses: actions/checkout@v2 20 | - name: Synchronize Issue Labels 21 | uses: ory/label-sync-action@v0 22 | with: 23 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 24 | dry: false 25 | forced: true 26 | -------------------------------------------------------------------------------- /.github/workflows/licenses.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/workflows/licenses.yml 3 | 4 | name: Licenses 5 | 6 | on: 7 | pull_request: 8 | push: 9 | branches: 10 | - main 11 | - v3 12 | - master 13 | 14 | jobs: 15 | licenses: 16 | name: License compliance 17 | runs-on: ubuntu-latest 18 | steps: 19 | - name: Install script 20 | uses: ory/ci/licenses/setup@master 21 | with: 22 | token: ${{ secrets.ORY_BOT_PAT || secrets.GITHUB_TOKEN }} 23 | - name: Check licenses 24 | uses: ory/ci/licenses/check@master 25 | - name: Write, commit, push licenses 26 | uses: ory/ci/licenses/write@master 27 | if: 28 | ${{ github.ref == 'refs/heads/main' || github.ref == 29 | 'refs/heads/master' || github.ref == 'refs/heads/v3' }} 30 | with: 31 | author-email: 32 | ${{ secrets.ORY_BOT_PAT && 33 | '60093411+ory-bot@users.noreply.github.com' || 34 | format('{0}@users.noreply.github.com', github.actor) }} 35 | author-name: ${{ secrets.ORY_BOT_PAT && 'ory-bot' || github.actor }} 36 | -------------------------------------------------------------------------------- /.github/workflows/stale.yml: -------------------------------------------------------------------------------- 1 | # AUTO-GENERATED, DO NOT EDIT! 2 | # Please edit the original at https://github.com/ory/meta/blob/master/templates/repository/common/.github/workflows/stale.yml 3 | 4 | name: "Close Stale Issues" 5 | on: 6 | workflow_dispatch: 7 | schedule: 8 | - cron: "0 0 * * *" 9 | 10 | jobs: 11 | stale: 12 | if: github.repository_owner == 'ory' 13 | runs-on: ubuntu-latest 14 | steps: 15 | - uses: actions/stale@v4 16 | with: 17 | repo-token: ${{ secrets.GITHUB_TOKEN }} 18 | stale-issue-message: | 19 | Hello contributors! 20 | 21 | I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue 22 | 23 | - open a PR referencing and resolving the issue; 24 | - leave a comment on it and discuss ideas on how you could contribute towards resolving it; 25 | - leave a comment and describe in detail why this issue is critical for your use case; 26 | - open a new issue with updated details and a plan for resolving the issue. 27 | 28 | Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic. 29 | 30 | Unfortunately, [burnout](https://www.jeffgeerling.com/blog/2016/why-i-close-prs-oss-project-maintainer-notes) has become a [topic](https://opensource.guide/best-practices/#its-okay-to-hit-pause) of [concern](https://docs.brew.sh/Maintainers-Avoiding-Burnout) amongst open-source projects. 31 | 32 | It can lead to severe personal and health issues as well as [opening](https://haacked.com/archive/2019/05/28/maintainer-burnout/) catastrophic [attack vectors](https://www.gradiant.org/en/blog/open-source-maintainer-burnout-as-an-attack-surface/). 33 | 34 | The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone. 35 | 36 | If this issue was marked as stale erroneously you can exempt it by adding the `backlog` label, assigning someone, or setting a milestone for it. 37 | 38 | Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you! 39 | 40 | Thank you 🙏✌️ 41 | stale-issue-label: "stale" 42 | exempt-issue-labels: "bug,blocking,docs,backlog" 43 | days-before-stale: 365 44 | days-before-close: 30 45 | exempt-milestones: true 46 | exempt-assignees: true 47 | only-pr-labels: "stale" 48 | -------------------------------------------------------------------------------- /.reference-ignore: -------------------------------------------------------------------------------- 1 | **/node_modules 2 | docs 3 | CHANGELOG.md 4 | -------------------------------------------------------------------------------- /.reports/dep-licenses.csv: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/.reports/dep-licenses.csv -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | # Contributor Covenant Code of Conduct 5 | 6 | ## Our Pledge 7 | 8 | We as members, contributors, and leaders pledge to make participation in our 9 | community a harassment-free experience for everyone, regardless of age, body 10 | size, visible or invisible disability, ethnicity, sex characteristics, gender 11 | identity and expression, level of experience, education, socio-economic status, 12 | nationality, personal appearance, race, caste, color, religion, or sexual 13 | identity and orientation. 14 | 15 | We pledge to act and interact in ways that contribute to an open, welcoming, 16 | diverse, inclusive, and healthy community. 17 | 18 | ## Our Standards 19 | 20 | Examples of behavior that contributes to a positive environment for our 21 | community include: 22 | 23 | - Demonstrating empathy and kindness toward other people 24 | - Being respectful of differing opinions, viewpoints, and experiences 25 | - Giving and gracefully accepting constructive feedback 26 | - Accepting responsibility and apologizing to those affected by our mistakes, 27 | and learning from the experience 28 | - Focusing on what is best not just for us as individuals, but for the overall 29 | community 30 | 31 | Examples of unacceptable behavior include: 32 | 33 | - The use of sexualized language or imagery, and sexual attention or advances of 34 | any kind 35 | - Trolling, insulting or derogatory comments, and personal or political attacks 36 | - Public or private harassment 37 | - Publishing others' private information, such as a physical or email address, 38 | without their explicit permission 39 | - Other conduct which could reasonably be considered inappropriate in a 40 | professional setting 41 | 42 | ## Open Source Community Support 43 | 44 | Ory Open source software is collaborative and based on contributions by 45 | developers in the Ory community. There is no obligation from Ory to help with 46 | individual problems. If Ory open source software is used in production in a 47 | for-profit company or enterprise environment, we mandate a paid support contract 48 | where Ory is obligated under their service level agreements (SLAs) to offer a 49 | defined level of availability and responsibility. For more information about 50 | paid support please contact us at sales@ory.sh. 51 | 52 | ## Enforcement Responsibilities 53 | 54 | Community leaders are responsible for clarifying and enforcing our standards of 55 | acceptable behavior and will take appropriate and fair corrective action in 56 | response to any behavior that they deem inappropriate, threatening, offensive, 57 | or harmful. 58 | 59 | Community leaders have the right and responsibility to remove, edit, or reject 60 | comments, commits, code, wiki edits, issues, and other contributions that are 61 | not aligned to this Code of Conduct, and will communicate reasons for moderation 62 | decisions when appropriate. 63 | 64 | ## Scope 65 | 66 | This Code of Conduct applies within all community spaces, and also applies when 67 | an individual is officially representing the community in public spaces. 68 | Examples of representing our community include using an official e-mail address, 69 | posting via an official social media account, or acting as an appointed 70 | representative at an online or offline event. 71 | 72 | ## Enforcement 73 | 74 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 75 | reported to the community leaders responsible for enforcement at 76 | [office@ory.sh](mailto:office@ory.sh). All complaints will be reviewed and 77 | investigated promptly and fairly. 78 | 79 | All community leaders are obligated to respect the privacy and security of the 80 | reporter of any incident. 81 | 82 | ## Enforcement Guidelines 83 | 84 | Community leaders will follow these Community Impact Guidelines in determining 85 | the consequences for any action they deem in violation of this Code of Conduct: 86 | 87 | ### 1. Correction 88 | 89 | **Community Impact**: Use of inappropriate language or other behavior deemed 90 | unprofessional or unwelcome in the community. 91 | 92 | **Consequence**: A private, written warning from community leaders, providing 93 | clarity around the nature of the violation and an explanation of why the 94 | behavior was inappropriate. A public apology may be requested. 95 | 96 | ### 2. Warning 97 | 98 | **Community Impact**: A violation through a single incident or series of 99 | actions. 100 | 101 | **Consequence**: A warning with consequences for continued behavior. No 102 | interaction with the people involved, including unsolicited interaction with 103 | those enforcing the Code of Conduct, for a specified period of time. This 104 | includes avoiding interactions in community spaces as well as external channels 105 | like social media. Violating these terms may lead to a temporary or permanent 106 | ban. 107 | 108 | ### 3. Temporary Ban 109 | 110 | **Community Impact**: A serious violation of community standards, including 111 | sustained inappropriate behavior. 112 | 113 | **Consequence**: A temporary ban from any sort of interaction or public 114 | communication with the community for a specified period of time. No public or 115 | private interaction with the people involved, including unsolicited interaction 116 | with those enforcing the Code of Conduct, is allowed during this period. 117 | Violating these terms may lead to a permanent ban. 118 | 119 | ### 4. Permanent Ban 120 | 121 | **Community Impact**: Demonstrating a pattern of violation of community 122 | standards, including sustained inappropriate behavior, harassment of an 123 | individual, or aggression toward or disparagement of classes of individuals. 124 | 125 | **Consequence**: A permanent ban from any sort of public interaction within the 126 | community. 127 | 128 | ## Attribution 129 | 130 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 131 | version 2.1, available at 132 | [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. 133 | 134 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 135 | enforcement ladder][mozilla coc]. 136 | 137 | For answers to common questions about this code of conduct, see the FAQ at 138 | [https://www.contributor-covenant.org/faq][faq]. Translations are available at 139 | [https://www.contributor-covenant.org/translations][translations]. 140 | 141 | [homepage]: https://www.contributor-covenant.org 142 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html 143 | [mozilla coc]: https://github.com/mozilla/diversity 144 | [faq]: https://www.contributor-covenant.org/faq 145 | [translations]: https://www.contributor-covenant.org/translations 146 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | # Contribute to Ory summit 5 | 6 | 7 | 8 | 9 | - [Introduction](#introduction) 10 | - [FAQ](#faq) 11 | - [How can I contribute?](#how-can-i-contribute) 12 | - [Communication](#communication) 13 | - [Contribute examples or community projects](#contribute-examples-or-community-projects) 14 | - [Contribute code](#contribute-code) 15 | - [Contribute documentation](#contribute-documentation) 16 | - [Disclosing vulnerabilities](#disclosing-vulnerabilities) 17 | - [Code style](#code-style) 18 | - [Working with forks](#working-with-forks) 19 | - [Conduct](#conduct) 20 | 21 | 22 | 23 | ## Introduction 24 | 25 | _Please note_: We take Ory summit's security and our users' trust very 26 | seriously. If you believe you have found a security issue in Ory summit, 27 | please disclose it by contacting us at security@ory.sh. 28 | 29 | There are many ways in which you can contribute. The goal of this document is to 30 | provide a high-level overview of how you can get involved in Ory. 31 | 32 | As a potential contributor, your changes and ideas are welcome at any hour of 33 | the day or night, on weekdays, weekends, and holidays. Please do not ever 34 | hesitate to ask a question or send a pull request. 35 | 36 | If you are unsure, just ask or submit the issue or pull request anyways. You 37 | won't be yelled at for giving it your best effort. The worst that can happen is 38 | that you'll be politely asked to change something. We appreciate any sort of 39 | contributions and don't want a wall of rules to get in the way of that. 40 | 41 | That said, if you want to ensure that a pull request is likely to be merged, 42 | talk to us! You can find out our thoughts and ensure that your contribution 43 | won't clash with Ory 44 | summit's direction. A great way to 45 | do this is via 46 | [Ory summit Discussions](https://github.com/orgs/ory/discussions) 47 | or the [Ory Chat](https://www.ory.sh/chat). 48 | 49 | ## FAQ 50 | 51 | - I am new to the community. Where can I find the 52 | [Ory Community Code of Conduct?](https://github.com/ory/summit/blob/master/CODE_OF_CONDUCT.md) 53 | 54 | - I have a question. Where can I get 55 | [answers to questions regarding Ory summit?](#communication) 56 | 57 | - I would like to contribute but I am not sure how. Are there 58 | [easy ways to contribute?](#how-can-i-contribute) 59 | [Or good first issues?](https://github.com/search?l=&o=desc&q=label%3A%22help+wanted%22+label%3A%22good+first+issue%22+is%3Aopen+user%3Aory+user%3Aory-corp&s=updated&type=Issues) 60 | 61 | - I want to talk to other Ory summit users. 62 | [How can I become a part of the community?](#communication) 63 | 64 | - I would like to know what I am agreeing to when I contribute to Ory 65 | summit. 66 | Does Ory have 67 | [a Contributors License Agreement?](https://cla-assistant.io/ory/summit) 68 | 69 | - I would like updates about new versions of Ory summit. 70 | [How are new releases announced?](https://www.ory.sh/l/sign-up-newsletter) 71 | 72 | ## How can I contribute? 73 | 74 | If you want to start to contribute code right away, take a look at the 75 | [list of good first issues](https://github.com/ory/summit/labels/good%20first%20issue). 76 | 77 | There are many other ways you can contribute. Here are a few things you can do 78 | to help out: 79 | 80 | - **Give us a star.** It may not seem like much, but it really makes a 81 | difference. This is something that everyone can do to help out Ory summit. 82 | Github stars help the project gain visibility and stand out. 83 | 84 | - **Join the community.** Sometimes helping people can be as easy as listening 85 | to their problems and offering a different perspective. Join our Slack, have a 86 | look at discussions in the forum and take part in community events. More info 87 | on this in [Communication](#communication). 88 | 89 | - **Answer discussions.** At all times, there are several unanswered discussions 90 | on GitHub. You can see an 91 | [overview here](https://github.com/discussions?discussions_q=is%3Aunanswered+org%3Aory+sort%3Aupdated-desc). 92 | If you think you know an answer or can provide some information that might 93 | help, please share it! Bonus: You get GitHub achievements for answered 94 | discussions. 95 | 96 | - **Help with open issues.** We have a lot of open issues for Ory summit and 97 | some of them may lack necessary information, some are duplicates of older 98 | issues. You can help out by guiding people through the process of filling out 99 | the issue template, asking for clarifying information or pointing them to 100 | existing issues that match their description of the problem. 101 | 102 | - **Review documentation changes.** Most documentation just needs a review for 103 | proper spelling and grammar. If you think a document can be improved in any 104 | way, feel free to hit the `edit` button at the top of the page. More info on 105 | contributing to the documentation [here](#contribute-documentation). 106 | 107 | - **Help with tests.** Pull requests may lack proper tests or test plans. These 108 | are needed for the change to be implemented safely. 109 | 110 | ## Communication 111 | 112 | We use [Slack](https://www.ory.sh/chat). You are welcome to drop in and ask 113 | questions, discuss bugs and feature requests, talk to other users of Ory, etc. 114 | 115 | Check out [Ory summit Discussions](https://github.com/orgs/ory/discussions). This is a great place for 116 | in-depth discussions and lots of code examples, logs and similar data. 117 | 118 | You can also join our community calls if you want to speak to the Ory team 119 | directly or ask some questions. You can find more info and participate in 120 | [Slack](https://www.ory.sh/chat) in the #community-call channel. 121 | 122 | If you want to receive regular notifications about updates to Ory summit, 123 | consider joining the mailing list. We will _only_ send you vital information on 124 | the projects that you are interested in. 125 | 126 | Also, [follow us on Twitter](https://twitter.com/orycorp). 127 | 128 | ## Contribute examples or community projects 129 | 130 | One of the most impactful ways to contribute is by adding code examples or other 131 | Ory-related code. You can find an overview of community code in the 132 | [awesome-ory](https://github.com/ory/awesome-ory) repository. 133 | 134 | _If you would like to contribute a new example, we would love to hear from you!_ 135 | 136 | Please [open a pull request at awesome-ory](https://github.com/ory/awesome-ory/) 137 | to add your example or Ory-related project to the awesome-ory README. 138 | 139 | ## Contribute code 140 | 141 | Unless you are fixing a known bug, we **strongly** recommend discussing it with 142 | the core team via a GitHub issue or [in our chat](https://www.ory.sh/chat) 143 | before getting started to ensure your work is consistent with Ory summit's 144 | roadmap and architecture. 145 | 146 | All contributions are made via pull requests. To make a pull request, you will 147 | need a GitHub account; if you are unclear on this process, see GitHub's 148 | documentation on [forking](https://help.github.com/articles/fork-a-repo) and 149 | [pull requests](https://help.github.com/articles/using-pull-requests). Pull 150 | requests should be targeted at the `master` branch. Before creating a pull 151 | request, go through this checklist: 152 | 153 | 1. Create a feature branch off of `master` so that changes do not get mixed up. 154 | 1. [Rebase](http://git-scm.com/book/en/Git-Branching-Rebasing) your local 155 | changes against the `master` branch. 156 | 1. Run the full project test suite with the `go test -tags sqlite ./...` (or 157 | equivalent) command and confirm that it passes. 158 | 1. Run `make format` 159 | 1. Add a descriptive prefix to commits. This ensures a uniform commit history 160 | and helps structure the changelog. Please refer to this 161 | [Convential Commits configuration](https://github.com/ory/summit/blob/master/.github/workflows/conventional_commits.yml) 162 | for the list of accepted prefixes. You can read more about the Conventional 163 | Commit specification 164 | [at their site](https://www.conventionalcommits.org/en/v1.0.0/). 165 | 166 | If a pull request is not ready to be reviewed yet 167 | [it should be marked as a "Draft"](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request). 168 | 169 | Before your contributions can be reviewed you need to sign our 170 | [Contributor License Agreement](https://cla-assistant.io/ory/summit). 171 | 172 | This agreement defines the terms under which your code is contributed to Ory. 173 | More specifically it declares that you have the right to, and actually do, grant 174 | us the rights to use your contribution. You can see the Apache 2.0 license under 175 | which our projects are published 176 | [here](https://github.com/ory/meta/blob/master/LICENSE). 177 | 178 | When pull requests fail the automated testing stages (for example unit or E2E 179 | tests), authors are expected to update their pull requests to address the 180 | failures until the tests pass. 181 | 182 | Pull requests eligible for review 183 | 184 | 1. follow the repository's code formatting conventions; 185 | 2. include tests that prove that the change works as intended and does not add 186 | regressions; 187 | 3. document the changes in the code and/or the project's documentation; 188 | 4. pass the CI pipeline; 189 | 5. have signed our 190 | [Contributor License Agreement](https://cla-assistant.io/ory/summit); 191 | 6. include a proper git commit message following the 192 | [Conventional Commit Specification](https://www.conventionalcommits.org/en/v1.0.0/). 193 | 194 | If all of these items are checked, the pull request is ready to be reviewed and 195 | you should change the status to "Ready for review" and 196 | [request review from a maintainer](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review). 197 | 198 | Reviewers will approve the pull request once they are satisfied with the patch. 199 | 200 | ## Contribute documentation 201 | 202 | Please provide documentation when changing, removing, or adding features. All 203 | Ory Documentation resides in the 204 | [Ory documentation repository](https://github.com/ory/docs/). For further 205 | instructions please head over to the Ory Documentation 206 | [README.md](https://github.com/ory/docs/blob/master/README.md). 207 | 208 | ## Disclosing vulnerabilities 209 | 210 | Please disclose vulnerabilities exclusively to 211 | [security@ory.sh](mailto:security@ory.sh). Do not use GitHub issues. 212 | 213 | ## Code style 214 | 215 | Please run `make format` to format all source code following the Ory standard. 216 | 217 | ### Working with forks 218 | 219 | ```bash 220 | # First you clone the original repository 221 | git clone git@github.com:ory/ory/summit.git 222 | 223 | # Next you add a git remote that is your fork: 224 | git remote add fork git@github.com:/ory/summit.git 225 | 226 | # Next you fetch the latest changes from origin for master: 227 | git fetch origin 228 | git checkout master 229 | git pull --rebase 230 | 231 | # Next you create a new feature branch off of master: 232 | git checkout my-feature-branch 233 | 234 | # Now you do your work and commit your changes: 235 | git add -A 236 | git commit -a -m "fix: this is the subject line" -m "This is the body line. Closes #123" 237 | 238 | # And the last step is pushing this to your fork 239 | git push -u fork my-feature-branch 240 | ``` 241 | 242 | Now go to the project's GitHub Pull Request page and click "New pull request" 243 | 244 | ## Conduct 245 | 246 | Whether you are a regular contributor or a newcomer, we care about making this 247 | community a safe place for you and we've got your back. 248 | 249 | [Ory Community Code of Conduct](https://github.com/ory/summit/blob/master/CODE_OF_CONDUCT.md) 250 | 251 | We welcome discussion about creating a welcoming, safe, and productive 252 | environment for the community. If you have any questions, feedback, or concerns 253 | [please let us know](https://www.ory.sh/chat). 254 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Andrew_Minkin_-__Using_Kratos_and_Keto_in_production_.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Andrew_Minkin_-__Using_Kratos_and_Keto_in_production_.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Ashley_Manraj_-_Customizing_Ory_Keto_with_global_scale_data_sharing_requirements.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Ashley_Manraj_-_Customizing_Ory_Keto_with_global_scale_data_sharing_requirements.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Bill_Monkman_-_Zero_Bootstrapping_SaaS_applications_leveraging_Ory_Kratos_and_Oathkeeper.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Bill_Monkman_-_Zero_Bootstrapping_SaaS_applications_leveraging_Ory_Kratos_and_Oathkeeper.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Christian_Roggia_-_Building_a_Google-like_IAM_system_from_scratch_through_Ory_products.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Christian_Roggia_-_Building_a_Google-like_IAM_system_from_scratch_through_Ory_products.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Dimitrij_Drus_-_Davids_Slingshot_-_Leveraging_Ory.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Dimitrij_Drus_-_Davids_Slingshot_-_Leveraging_Ory.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Keynote_-_Future_Directions_for_the_New_ID_Stack.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Keynote_-_Future_Directions_for_the_New_ID_Stack.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_1_-_Sashi_Deshetti_Kavach_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_1_-_Sashi_Deshetti_Kavach_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_Akibur_Rahman_-_Implementing_the_Ory_stack_at_Padis.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_Akibur_Rahman_-_Implementing_the_Ory_stack_at_Padis.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_Amorevino_-_Ory-Cloud_Service_for_App_Developers.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_Amorevino_-_Ory-Cloud_Service_for_App_Developers.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_David_Alexander_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_David_Alexander_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_Dirk_Riehle_-_Open_Source_License_Compliance_and_Ory_Open_Source.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_Dirk_Riehle_-_Open_Source_License_Compliance_and_Ory_Open_Source.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_Jakob_Sinclair_-_Building_a_community_management_infrastructure_with_Ory_open_source_software.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_Jakob_Sinclair_-_Building_a_community_management_infrastructure_with_Ory_open_source_software.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_Keynote_-_Ory_Cloud_Technical_Direction.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_Keynote_-_Ory_Cloud_Technical_Direction.pdf -------------------------------------------------------------------------------- /Ory_Summit_21_Day_2_-_Stepan_Rakitin_-_SumUp_Self-service_OIDC_for_with_Ory_Hydra_and_Terraform.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_21_Day_2_-_Stepan_Rakitin_-_SumUp_Self-service_OIDC_for_with_Ory_Hydra_and_Terraform.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Aeneas_Rekkas_Klaus_Herrman_-_Introducing_the_Ory_Network.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Aeneas_Rekkas_Klaus_Herrman_-_Introducing_the_Ory_Network.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Amorevino_-_Delightful_auth_experience_for_social_e-commerce_apps.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Amorevino_-_Delightful_auth_experience_for_social_e-commerce_apps.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Artur_Balsam_-_Threat_Modelling_101.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Artur_Balsam_-_Threat_Modelling_101.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Bobur_Umurzokov_-_Centralized Authentication with Apache APISIX and Ory.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Bobur_Umurzokov_-_Centralized Authentication with Apache APISIX and Ory.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Deniz_Onur_Duzgun_-_Make_Auth_Great_Again_With_Ory.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Deniz_Onur_Duzgun_-_Make_Auth_Great_Again_With_Ory.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Harri_Hursti_-_Zero_Trust_Now_we_must_but_what_it_means.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Harri_Hursti_-_Zero_Trust_Now_we_must_but_what_it_means.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Ilya_Migal_Dominik_Lekse_-_One_auth_gateway_to_authenticate_them_all.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Ilya_Migal_Dominik_Lekse_-_One_auth_gateway_to_authenticate_them_all.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Lloyd_W_Taylor_-_Building_applications_in_the_cloud.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Lloyd_W_Taylor_-_Building_applications_in_the_cloud.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Lukasz_Harasimowicz_-_Running_Ory_on_30M_user_platform.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Lukasz_Harasimowicz_-_Running_Ory_on_30M_user_platform.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Mal_Curtis_Ory_in_the_inMusic_cloud.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Mal_Curtis_Ory_in_the_inMusic_cloud.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Patrick_Neu_Henning_Perl_-_Making_of_the_Ory_Permission_Language.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Patrick_Neu_Henning_Perl_-_Making_of_the_Ory_Permission_Language.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Shota_Sawada_-_Replaceing_Identity_Server_with_Ory.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Shota_Sawada_-_Replaceing_Identity_Server_with_Ory.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Thomas_Curran_-_Securing_the_digital_world.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Thomas_Curran_-_Securing_the_digital_world.pdf -------------------------------------------------------------------------------- /Ory_Summit_22_-_Xavier_Vello_-_Designing_OSS_project_for_low_maintenance.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/Ory_Summit_22_-_Xavier_Vello_-_Designing_OSS_project_for_low_maintenance.pdf -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Ory Summit 2 | 3 | Ory Summit is a developer conference organized by Ory and the Ory Community. 4 | 5 | Ory Summit provides opportunities to trade insights and experience on best practices, emerging new methods, approaches, and practical solutions around identity and access management in the cloud. 6 | 7 | ## Ory Summit 2023 8 | 9 | ### 9th November 2023 10 | 11 | **[Get your ticket for Ory Summit 2023 here!](https://summit.ory.sh/)** 12 | 13 | A one-day conference around open source end-to-end security and zero trust solutions for the Ory Community - customers, developers, maintainers, and partners. 14 | 15 | ## Ory Summit 2022 16 | 17 | ![ory summit 22 banner](./img/2022-spotlight-banner-989x400.png) 18 | 19 | In this repository you can find all publicly available material related to the Ory Summit 2022. 20 | 21 | In the Ory Summit 2021 Session Overview you can find recordings and slides for all presentations. 22 | 23 | **!---> [Full Ory Summit 2022 Playlist](https://www.youtube.com/playlist?list=PLZ-V_cBgMxH8b1V53hJ1avMYrV6te799i) <---!** 24 | 25 | ### Ory Summit 20221 Session Overview 26 | 27 | An overview of all the sessions and where they can be found to watch after the summit. 28 | 29 | **Ory Summit 22** 30 | 31 | October 20 2022: 09.30-18.00 CET 32 | 33 | --- 34 | 35 | #### Keynote: Securing the digital World 36 | 37 | - [@tacurran](https://github.com/tacurran), Co-founder & CEO of Ory Corp 38 | 39 | Recording: https://www.youtube.com/watch?v=wo7eZREQg9s 40 | 41 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Thomas_Curran_-_Securing_the_digital_world.pdf) 42 | 43 | --- 44 | 45 | #### Keynote: Introducing the Ory Network 46 | 47 | - [@aeneasr](https://github.com/aeneasr), Co-founder & CEO of Ory Corp 48 | 49 | Recording: https://www.youtube.com/watch?v=26dC2nvK978 50 | 51 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Aeneas_Rekkas_Klaus_Herrman_-_Introducing_the_Ory_Network.pdf) 52 | 53 | --- 54 | 55 | #### Building applications in the Cloud 56 | 57 | - [@lloyd-taylor](https://github.com/lloyd-taylor) 58 | 59 | Recording: https://www.youtube.com/watch?v=8vsdJ2W97yM 60 | 61 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Lloyd_W_Taylor_-_Building_applications_in_the_cloud.pdf) 62 | 63 | --- 64 | 65 | #### Ory in the inMusic Cloud 66 | 67 | - [@snikch](https://github.com/snikch) 68 | 69 | Recording: https://www.youtube.com/watch?v=knSj-x4AV-w 70 | 71 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Thomas_Curran_-_Securing_the_digital_world.pdf) 72 | 73 | --- 74 | 75 | #### Centralized Authentication with Apache APISIX and Ory 76 | 77 | - [@Boburmirzo](https://github.com/Boburmirzo) 78 | 79 | Recording: https://www.youtube.com/watch?v=oYXpD-5044k 80 | 81 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Bobur_Umurzokov_-_Centralized%20Authentication%20with%20Apache%20APISIX%20and%20Ory.pdf) 82 | 83 | --- 84 | 85 | #### Running Ory on a 30M users platform 86 | 87 | - [@harnash](https://github.com/harnash) 88 | 89 | Recording: https://www.youtube.com/watch?v=i-P6EOo7SGc 90 | 91 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Lukasz_Harasimowicz_-_Running_Ory_on_30M_user_platform.pdf) 92 | 93 | --- 94 | 95 | #### Making of the Ory Permissions Language 96 | 97 | - [@zepatrik](https://github.com/zepatrik) 98 | - [@hperl](https://github.com/hperl) 99 | 100 | Recording: https://www.youtube.com/watch?v=7Tz_8ekYCjs 101 | 102 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Patrick_Neu_Henning_Perl_-_Making_of_the_Ory_Permission_Language.pdf) 103 | 104 | --- 105 | 106 | #### Make Auth great again with Ory 107 | 108 | - [@dduzgun-security](https://github.com/dduzgun-security) 109 | 110 | Recording: https://www.youtube.com/watch?v=ivK6igAWlBo 111 | 112 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Deniz_Onur_Duzgun_-_Make_Auth_Great_Again_With_Ory.pdf) 113 | 114 | --- 115 | 116 | #### Delightful auth experience for social e-commerce Apps 117 | 118 | - [@sofiadipace](https://github.com/sofiadipace) 119 | - [@Amorevino](https://github.com/amorevino) 120 | 121 | Recording: https://www.youtube.com/watch?v=gJwtyKDsLTo 122 | 123 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Amorevino_-_Delightful_auth_experience_for_social_e-commerce_apps.pdf) 124 | 125 | --- 126 | 127 | #### How TIER IV Replaced Identity Server with Ory 128 | 129 | - [@sawadashota](https://github.com/sawadashota) 130 | 131 | Recording: https://www.youtube.com/watch?v=umQte31KIAY 132 | 133 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Shota_Sawada_-_Replaceing_Identity_Server_with_Ory.pdf) 134 | 135 | --- 136 | 137 | #### Threat Modelling 101 138 | 139 | - [@schreddies](https://github.com/schreddies) 140 | 141 | Recording: https://www.youtube.com/watch?v=yHf9Z-eKc0U 142 | 143 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Artur_Balsam_-_Threat_Modelling_101.pdf) 144 | 145 | --- 146 | 147 | #### Zero Trust Architecture - Now We Must, But What It Means? 148 | 149 | - [@scof](https://github.com/scof) 150 | 151 | Recording: https://www.youtube.com/watch?v=AvqcM36g5hg 152 | 153 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Harri_Hursti_-_Zero_Trust_Now_we_must_but_what_it_means.pdf) 154 | 155 | --- 156 | 157 | #### One Auth Gateway to authenticate them all 158 | 159 | - [dominik-lekse](https://github.com/dominik-lekse) 160 | 161 | Recording: https://www.youtube.com/watch?v=eJhGgY9TVHQ 162 | 163 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Ilya_Migal_Dominik_Lekse_-_One_auth_gateway_to_authenticate_them_all.pdf) 164 | 165 | --- 166 | 167 | #### Designing an open-source project for low maintenance 168 | 169 | - [xvello](https://github.com/xvello) 170 | 171 | Recording: https://www.youtube.com/watch?v=ROFt3xUI0tM 172 | 173 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_22_-_Xavier_Vello_-_Designing_OSS_project_for_low_maintenance.pdf) 174 | 175 | --- 176 | 177 | ## Ory Summit 2021 178 | 179 | ![ory summit 21 banner](./img/spotlight-banner-1920x400.png) 180 | 181 | In this repository you can find all publicly available material related to the Ory Summit 2021. 182 | 183 | In the Ory Summit 2021 Session Overview you can find recordings and slides for all presentations. 184 | 185 | **!---> [Full Ory Summit 2021 Playlist](https://www.youtube.com/watch?v=rD4G7cA-Af0&list=PLZ-V_cBgMxH9b8ziEKu7wcpPlkgLU-3rQ) <---!** 186 | 187 | ### Ory Summit 2021 Session Overview 188 | 189 | An overview of all the sessions and where they can be found to watch after the summit. 190 | 191 | **Ory Summit 21 West** 192 | October 28 2021: 15.30-20.00 CET 193 | 194 | --- 195 | 196 | #### Keynote: Open Source and Beyond 197 | 198 | Kick-off: Ory Summit West - Day One 199 | Speakers: 200 | 201 | - [@tacurran](https://github.com/tacurran), Co-founder & CEO of Ory Corp 202 | - [@aeneasr](https://github.com/aeneasr), Co-founder & CEO of Ory Corp 203 | 204 | Recording: https://www.youtube.com/watch?v=rD4G7cA-Af0 205 | 206 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Keynote_-_Future_Directions_for_the_New_ID_Stack.pdf) 207 | 208 | --- 209 | 210 | #### Building a Google-like IAM System from Scratch Through Ory Products 211 | 212 | Speaker: 213 | 214 | - [@christian-roggia](https://github.com/christian-roggia), CEO of Animeshon 215 | 216 | Recording: https://www.youtube.com/watch?v=lsH2dYh-_3g 217 | 218 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Christian_Roggia_-_Building_a_Google-like_IAM_system_from_scratch_through_Ory_products.pdf) 219 | 220 | --- 221 | 222 | #### David's Slingshot - Leveraging Ory 223 | 224 | Speaker: 225 | 226 | - [@dadrus](https://github.com/dadrus), Senior Consultant at INNOQ 227 | 228 | Recording: https://www.youtube.com/watch?v=ZzZgU7w5ZjY 229 | 230 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Dimitrij_Drus_-_Davids_Slingshot_-_Leveraging_Ory.pdf) 231 | 232 | --- 233 | 234 | #### Customizing Ory Keto with Global-scale Custom Data Sharing Requirements 235 | 236 | Speaker: 237 | 238 | - Ashley Manraj, CTO at Pvotal 239 | 240 | Recording: https://www.youtube.com/watch?v=A_IH_1NW7cM 241 | 242 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Ashley_Manraj_-_Customizing_Ory_Keto_with_global_scale_data_sharing_requirements.pdf) 243 | 244 | --- 245 | 246 | `Workshop` 247 | 248 | #### Design Complex Authorization with Ory Keto 249 | 250 | Speaker: 251 | 252 | - [@zepatrik](https://github.com/zepatrik), Engineer at Ory Corp 253 | 254 | Recording: https://www.youtube.com/watch?v=lGRMYkQrNb0 255 | 256 | Presentation & Repository: [zepatrik/ory-summit21-talk](https://github.com/zepatrik/ory-summit21-talk) 257 | 258 | --- 259 | 260 | #### A history of re-engineering: using Ory Kratos and Ory Keto in production 261 | 262 | Speaker: 263 | 264 | - [@gen1us2k](https://github.com/gen1us2k) 265 | 266 | Recording: https://www.youtube.com/watch?v=WMjcsOC2W28 267 | 268 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Andrew_Minkin_-__Using_Kratos_and_Keto_in_production_.pdf) 269 | 270 | --- 271 | 272 | #### Kavach: An Open-source Identity Platform Built on Ory 273 | 274 | Speaker: 275 | 276 | - Shashi Deshetti, CTO at Factly 277 | 278 | Recording: https://www.youtube.com/watch?v=yOCfp5ylTzs 279 | 280 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Sashi_Deshetti_Kavach_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf) 281 | 282 | --- 283 | 284 | #### Zero: Bootstrapping SaaS applications featuring Ory Kratos and Oathkeeper 285 | 286 | Speaker: 287 | 288 | - [@bmonkman](https://github.com/bmonkman), Chief Architect at Commit 289 | 290 | Recording: https://www.youtube.com/watch?v=KIhs2gSF-2s 291 | 292 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_1_-_Bill_Monkman_-_Zero_Bootstrapping_SaaS_applications_leveraging_Ory_Kratos_and_Oathkeeper.pdf) 293 | 294 | --- 295 | 296 | #### Recap + Closing Remarks 297 | 298 | Speaker: 299 | 300 | - [@tacurran](https://github.com/tacurran), Co-founder & CEO of Ory Corp 301 | 302 | --- 303 | 304 | **Ory Summit 21 East** 305 | October 29 2021: 9.30-14.00 CET 306 | 307 | --- 308 | 309 | #### Ory Cloud (Technical Direction) 310 | 311 | - Kick-off: Ory Summit East - Day Two 312 | Speakers: 313 | - [@tricky42](https://github.com/tricky42), Head of Engineering at Ory Corp 314 | - [@tacurran](https://github.com/tacurran), Co-founder & CEO of Ory Corp 315 | 316 | Recording: https://www.youtube.com/watch?v=3veok1v4LfE 317 | 318 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_Keynote_-_Ory_Cloud_Technical_Direction.pdf) 319 | 320 | --- 321 | 322 | #### Implementing the Ory Stack at Padis: A Journey 323 | 324 | Speaker: 325 | 326 | - Akibur Rahman, System Architect at Padis.io 327 | 328 | Recording: https://www.youtube.com/watch?v=2-fjsM1yx0Q 329 | 330 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_Akibur_Rahman_-_Implementing_the_Ory_stack_at_Padis.pdf) 331 | 332 | --- 333 | 334 | #### Ory Cloud Service for Application Developers and a Practical Example Featuring Firebase 335 | 336 | Speakers: 337 | 338 | - [@tc-amorevino](https://github.com/tc-amorevino) & 339 | - Tilman Theile, Co-founders of Amorevino ([GitHub](https://github.com/amorevino/)). 340 | 341 | Recording: https://www.youtube.com/watch?v=WC6CFiSU1bw 342 | 343 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_Amorevino_-_Ory-Cloud_Service_for_App_Developers.pdf) 344 | 345 | **Blog & Video Tutorial: E-Commerce with Ory Cloud** 346 | 347 | - [Part 1: Backend Example](https://www.ory.sh/cloud-ecommerce-backend/) 348 | - [Part 2: Frontend Example](https://www.ory.sh/cloud-ecommerce-frontend/) 349 | 350 | --- 351 | 352 | #### Open Source License Compliance and Ory Open Source 353 | 354 | Speaker: 355 | 356 | - [@dirkriehle](https://github.com/dirkriehle), Professor of Open Source Software at the Friedrich-Alexander University of Erlangen-Nürnberg 357 | 358 | Recording: https://www.youtube.com/watch?v=0DkVA3X0lhQ 359 | 360 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_Dirk_Riehle_-_Open_Source_License_Compliance_and_Ory_Open_Source.pdf) 361 | 362 | --- 363 | 364 | #### SumUp Self-service OIDC Using Ory Hydra and Terraform 365 | 366 | Speaker: 367 | 368 | - [@svrakitin](https://github.com/svrakitin), Platform Engineer at SumUp 369 | 370 | Recording: https://www.youtube.com/watch?v=O3mtX2cciHc 371 | 372 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_Stepan_Rakitin_-_SumUp_Self-service_OIDC_for_with_Ory_Hydra_and_Terraform.pdf) 373 | 374 | --- 375 | 376 | #### Building Community Management Infrastructure with Ory Open Source Software 377 | 378 | Speaker: 379 | 380 | - Jakob Sinclair, IT-expert for Piratpartiet 381 | 382 | Recording: https://www.youtube.com/watch?v=8KGdp4SCKQc 383 | 384 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_Jakob_Sinclair_-_Building_a_community_management_infrastructure_with_Ory_open_source_software.pdf) 385 | 386 | --- 387 | 388 | #### Empowering No-code Application Development Lifecycle Using Ory 389 | 390 | Speaker: 391 | 392 | - [@david972](https://github.com/david972), CTO at Wildcard (w6d.io) 393 | 394 | Recording: https://www.youtube.com/watch?v=YdBR5hscIz4 395 | 396 | Presentation: [View & Download Slides](https://github.com/ory/summit/blob/master/Ory_Summit_21_Day_2_-_David_Alexander_-_Empowering_no-code_application_development_using_Ory_Kratos_and_Ory_Keto.pdf) 397 | 398 | --- 399 | 400 | - [Sign up for Ory Cloud](https://console.ory.sh/) 401 | 402 | **See you next year!** 403 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | # Ory Security Policy 5 | 6 | This policy outlines Ory's security commitments and practices for users across 7 | different licensing and deployment models. 8 | 9 | To learn more about Ory's security service level agreements (SLAs) and 10 | processes, please [contact us](https://www.ory.sh/contact/). 11 | 12 | ## Ory Network Users 13 | 14 | - **Security SLA:** Ory addresses vulnerabilities in the Ory Network according 15 | to the following guidelines: 16 | - Critical: Typically addressed within 14 days. 17 | - High: Typically addressed within 30 days. 18 | - Medium: Typically addressed within 90 days. 19 | - Low: Typically addressed within 180 days. 20 | - Informational: Addressed as necessary. 21 | These timelines are targets and may vary based on specific circumstances. 22 | - **Release Schedule:** Updates are deployed to the Ory Network as 23 | vulnerabilities are resolved. 24 | - **Version Support:** The Ory Network always runs the latest version, ensuring 25 | up-to-date security fixes. 26 | 27 | ## Ory Enterprise License Customers 28 | 29 | - **Security SLA:** Ory addresses vulnerabilities based on their severity: 30 | - Critical: Typically addressed within 14 days. 31 | - High: Typically addressed within 30 days. 32 | - Medium: Typically addressed within 90 days. 33 | - Low: Typically addressed within 180 days. 34 | - Informational: Addressed as necessary. 35 | These timelines are targets and may vary based on specific circumstances. 36 | - **Release Schedule:** Updates are made available as vulnerabilities are 37 | resolved. Ory works closely with enterprise customers to ensure timely updates 38 | that align with their operational needs. 39 | - **Version Support:** Ory may provide security support for multiple versions, 40 | depending on the terms of the enterprise agreement. 41 | 42 | ## Apache 2.0 License Users 43 | 44 | - **Security SLA:** Ory does not provide a formal SLA for security issues under 45 | the Apache 2.0 License. 46 | - **Release Schedule:** Releases prioritize new functionality and include fixes 47 | for known security vulnerabilities at the time of release. While major 48 | releases typically occur one to two times per year, Ory does not guarantee a 49 | fixed release schedule. 50 | - **Version Support:** Security patches are only provided for the latest release 51 | version. 52 | 53 | ## Reporting a Vulnerability 54 | 55 | For details on how to report security vulnerabilities, visit our 56 | [security policy documentation](https://www.ory.sh/docs/ecosystem/security). 57 | -------------------------------------------------------------------------------- /img/2022-spotlight-banner-989x400.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/img/2022-spotlight-banner-989x400.png -------------------------------------------------------------------------------- /img/banner-1280x400.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/img/banner-1280x400.png -------------------------------------------------------------------------------- /img/logo-300x300.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/img/logo-300x300.png -------------------------------------------------------------------------------- /img/small-banner-385x250.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/img/small-banner-385x250.png -------------------------------------------------------------------------------- /img/spotlight-banner-1920x400.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/img/spotlight-banner-1920x400.png -------------------------------------------------------------------------------- /wallpaper/abstract/ory-wallpaper-abstract-1-dark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/abstract/ory-wallpaper-abstract-1-dark.png -------------------------------------------------------------------------------- /wallpaper/abstract/ory-wallpaper-abstract-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/abstract/ory-wallpaper-abstract-1.png -------------------------------------------------------------------------------- /wallpaper/abstract/ory-wallpaper-abstract-2-dark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/abstract/ory-wallpaper-abstract-2-dark.png -------------------------------------------------------------------------------- /wallpaper/abstract/ory-wallpaper-abstract-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/abstract/ory-wallpaper-abstract-2.png -------------------------------------------------------------------------------- /wallpaper/abstract/ory-wallpaper-abstract-3-dark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/abstract/ory-wallpaper-abstract-3-dark.png -------------------------------------------------------------------------------- /wallpaper/abstract/ory-wallpaper-abstract-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/abstract/ory-wallpaper-abstract-3.png -------------------------------------------------------------------------------- /wallpaper/ory-digital-mountain-1920x1200.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/ory-digital-mountain-1920x1200.png -------------------------------------------------------------------------------- /wallpaper/ory-digital-mountain-2880x1800.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/ory-digital-mountain-2880x1800.png -------------------------------------------------------------------------------- /wallpaper/ory-summit-1920x1200.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/ory-summit-1920x1200.png -------------------------------------------------------------------------------- /wallpaper/ory-summit-2880x1800.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/ory-summit-2880x1800.png -------------------------------------------------------------------------------- /wallpaper/ory-wallpaper-2022-2560x1440.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/ory-wallpaper-2022-2560x1440.png -------------------------------------------------------------------------------- /wallpaper/ory-wallpaper-wide.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ory/summit/11ae2aed8b93e0dadde3dd922be4dc451313182a/wallpaper/ory-wallpaper-wide.jpg --------------------------------------------------------------------------------