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

Hey <@U01F2C4EA02>
the old SDK should work just fine!
or have you been running into trouble using it with the new version?

we get a handful of errors like this every day:
`response status code does not match any response statuses defined for this endpoint in the swagger spec (status 409): {}`

I assume that's because the service is returning a status code that the SDK doesn't understand. maybe I've wrongly assumed that would be fixed by a new client

I see. Could you open an issue for it, that is probably the best way to resolve this:
<https://github.com/ory/hydra/issues/new?assignees=&amp;labels=bug&amp;template=BUG-REPORT.yml>

just going over the latest breaking changes:

• Endpoint `PUT /clients` now returns a 404 error when the OAuth2 Client to be updated does not exist. It returned 401 previously. This change requires you to run SQL migrations!
and in v10.2
• This patch makes it so that already handled consent/login/logout requests respond with 410 Gone instead of 409 Conflict. Additionally, a URL is included that the user should be redirected to!

I may have missed something, but I think there should be no problem with the SDK :thinking_face: