Releases: clerk/clerk-sdk-ruby
3.3.0 - Session re-verification
This release adds helpers to support the session re-verification flow (also known as Step Up).
Added
- Helpers for implementing re-verification flows #72:
clerk_user_needs_reverification?
: Returnstrue
if the user must be re-verifiedclerk_render_reverification
: Renders the JSON response required by Clerk.js to kickstart a re-verification flow. Meant to be called in a Rails controller action.Clerk::StepUp::PRESETS
: contains configuration presets for passing toclerk_user_needs_reverification?
clerk_reverification_response
can be used to return the response from a Rack middleware
Session re-verification (beta)
This release adds various helpers to support the session re-verification flow (also known as Step Up).
Added
- Helpers for implementing re-verification flows #72:
clerk_user_needs_reverification?
: Returnstrue
if the user must be re-verifiedclerk_render_reverification
: Renders the JSON response required by Clerk.js to kickstart a re-verification flow. Meant to be called in a Rails controller action.Clerk::StepUp::PRESETS
: contains configuration presets for passing toclerk_user_needs_reverification?
clerk_reverification_response
can be used to return the response from a Rack middleware
3.0.0
2.11.1
Faraday v2 support
Changes
- Added support for Faraday v2 [#37]
2.9.0
Fixes
- Proper caching of JWKS responses [#27]
Changes
- All requests to the Backend API now use
application/json
payloads. This also fixes particular calls to endpoints like theuser.update
request when passing in backup codes [#29]
Additions
- The API key can now be set using the
CLERK_SECRET_KEY
environment variable [#28]
v2.9.0.beta3
Changed
- internal: Change request payloads to
application/json
content type [#29]
Secret Key support
Added
- Support setting the secret key (previously called Backend API key) using the
CLERK_SECRET_KEY
environment variable [#28]
In-memory shared JWKS cache
This is a bugfix release that fixes the JWKS cache to actually be re-used across incoming requests that the auth middleware processes. Previously, the cache wasn't working as intended after 1123911, since the middleware was always constructing a new SDK instance.
That said, since this is significant change in behavior, make sure to test this release in your development environment before upgrading in production.
Users/VerifyTOTP
Added
- Support for the users.verify_totp operation