Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi all. New guy here. I’ve got a PR for Fosite and a matching one for Hydra. Currently, CI is failing conformity tests because it looks like it is trying to use my new change with the master version of Hydra. I’ve added a new field to fosite.Config so it is causing an error. Maybe I added it in the wrong places? I’m just getting used to this codebase. <https://github.com/ory/fosite/pull/733>

Hydra one is a WIP because I don’t know how the go.mod version should be changed. <https://github.com/ory/hydra/compare/master...mattslocum:hydra:custom_token_prefix?expand=1>

Here is an example of a change which changes the go.mod of hydra to use a public PR. Basically you add a replace for `<http://github.com/ory/fosite|github.com/ory/fosite>` to `&lt;your fork&gt;` with the latest commit sha1 as the version then you can run `go mod tidy`
. In my instance I used the following and go adjusted it to what you see in the PR content.

`replace <http://github.com/ory/fosite|github.com/ory/fosite> =&gt; <http://github.com/james-d-elliott/fosite|github.com/james-d-elliott/fosite> 1b13725b705506e8dffba80ee09f3ed32227299c`

There is potentially another way to achieve it but that's the way I found that worked effectively.