Skip to content

Releases: ory/fosite

v0.35.1

20 Oct 10:33
Compare
Choose a tag to compare
autogen(docs): regenerate and update changelog

v0.35.0

07 Oct 11:18
Compare
Choose a tag to compare
autogen(docs): regenerate and update changelog

v0.34.1

02 Oct 13:17
Compare
Choose a tag to compare
fix: make redirect URL checking more strict

The OAuth 2.0 Client's Redirect URL and the Redirect URL used in the OAuth 2.0 flow do not check if the query string is equal:

1. Registering a client with allowed redirect URL `https://example.com/callback`
2. Performing OAuth2 flow and requesting redirect URL `https://example.com/callback?bar=foo`
3. Instead of an error, the browser is redirected to `https://example.com/callback?bar=foo` with a potentially successful OAuth2 response.

Additionally, matching Redirect URLs used `strings.ToLower` normalization:

1. Registering a client with allowed redirect URL `https://example.com/callback`
2. Performing OAuth2 flow and requesting redirect URL `https://example.com/CALLBACK`
3. Instead of an error, the browser is redirected to `https://example.com/CALLBACK ` with a potentially successful OAuth2 response.

This patch addresses all of these issues and adds regression tests to keep the implementation secure in future releases.

v0.34.0

24 Sep 13:23
3540462
Compare
Choose a tag to compare
chore: fix unused const linter error (#484)

v0.33.0

16 Sep 09:27
8daab21
Compare
Choose a tag to compare
feat: error_hint and error_debug are now exposed through error_descri…

v0.32.4

15 Sep 11:21
Compare
Choose a tag to compare
autogen(docs): regenerate and update changelog

v0.32.3

12 Sep 11:02
88587fd
Compare
Choose a tag to compare
fix: add missing OAuth2TokenRevocationFactory to ComposeAllEnabled (#…

v0.32.2

23 Jun 07:19
901e206
Compare
Choose a tag to compare
feat: new factory with default issuer for JWT tokens (#444)

v0.32.1

05 Jun 06:34
17b0756
Compare
Choose a tag to compare
feat: makeRemoveEmpty public (#443)

v0.32.0

28 May 13:57
36eb661
Compare
Choose a tag to compare

Adds the ability to use ECDSA keys for client authentication as well as RSA. Additionally resolves an issue with double-encoding client IDs and secrets in POST bodies.