Skip to content

reddont v0.1.19

Latest

Choose a tag to compare

@voc0der voc0der released this 21 Nov 13:39
e2eeef6

๐Ÿš€ reddont 0.1.19

A fix for signing in through an OIDC provider on another domain.

๐Ÿ› ๏ธ Fixes

  • OIDC sign-in loop with a provider on another site. With the provider on a different domain from reddont, signing in sent the browser back to the provider over and over until it reported too many redirects. The session cookie is now SameSite=Lax rather than Strict, so the browser sends it on the provider's redirect home. A link to reddont from another site now opens signed in too. Before, it started the same loop, even with the provider on reddont's own domain. #116, fixes #114

๐Ÿ”„ Changed

  • Creating an invite is a button. It's now a form with a CSRF token, not a link, as deleting one became in 0.1.17. The session cookie now comes along on links from other sites, so a link elsewhere could otherwise have made an administrator create an invite. Every form still needs the CSRF token, whose cookie stays SameSite=Strict. #116

๐Ÿ“ฆ Under the hood

  • Coverage. JavaScript line coverage is 98.39%, with all 496 tests passing and none skipped. #116

โš ๏ธ Before you upgrade

  • Update the image to ghcr.io/voc0der/reddont:0.1.19, or follow :latest.
  • Nobody has to sign in again. Existing sessions keep working, and each session's cookie becomes Lax at its next sign-in. If you worked around the loop with nginx's proxy_cookie_flags __Host-auth_token samesite=lax, you can remove it.

Full Changelog: v0.1.18...v0.1.19

Release contributors: @voc0der