Skip to content

Releases: curveball/a12n-server

v0.27.5

11 Dec 03:15
29f56b7
Compare
Choose a tag to compare

v0.27.4

06 Dec 21:02
632446d
Compare
Choose a tag to compare
  • Schemas misspelled as 'schema'. Sorry for all the releases, I dont know to do a clean test of npx without doing a release first, so the feedback loop is change->release->test.

v0.27.3

06 Dec 20:59
f193678
Compare
Choose a tag to compare
  • Copy simplewebauthn browser bundle into assets directory for easier distribution.

v0.27.2

06 Dec 20:47
98ce843
Compare
Choose a tag to compare
  • Fix missing entries in files section in package.json, preventing the npx @curveball/a12n-server tool from working.

v0.27.1

06 Dec 05:00
32457b9
Compare
Choose a tag to compare
  • Fix HTTP/500 error when requesting a developer access token.

v0.27.0

05 Dec 22:30
9d5ffbd
Compare
Choose a tag to compare
  • authorization_challenge now supports a TOTP challenge step!
  • Refactored logging system. Less ugly now with fewer enums!
  • authorization_challenge clients can now specify remote_addr and user_agent, so the server can keep accurate logs of the users' browser that's trying to authenticate.
  • Return the correct 'ttl' value for a verification-token.
  • Instead of 1 generic error with a few parameters, the server now emits invididual error codes for each kind of error that may be emitted from the authorization_challenge endpoint. This is change is based on examples in more recent drafts and should simplify the process for clients a bit. This is a BC break for authorization_challenge.
  • Renamed login_failed event to password-check-failed.
  • Added events: password-check-succes, totp-success, login-challenge-started, login-challenge-success

v0.26.7

07 Nov 19:28
47a762a
Compare
Choose a tag to compare
  • Updated Curveball dependencies. CURVEBALL_TRUSTPROXY should now work as expected.

v0.26.6

06 Nov 21:28
d71d57c
Compare
Choose a tag to compare
  • Updated Curveball dependencies

v0.26.5

30 Oct 05:24
6a59e51
Compare
Choose a tag to compare
  • Developer tokens will now be associated with a client_id if an OAuth2 client was used to generate one. This allows them to be refreshed.
  • A scope can now be specified when creating a developer token.

v0.26.4

28 Oct 21:20
1dc4444
Compare
Choose a tag to compare
  • New: access-token endpoint now returns refresh token.