Skip to content

feat(meta): add per-method MFA availability fields + bump 3.3.0-rc.1#44

Merged
lakhansamani merged 1 commit into
mainfrom
feat/meta-mfa-method-fields
Jul 12, 2026
Merged

feat(meta): add per-method MFA availability fields + bump 3.3.0-rc.1#44
lakhansamani merged 1 commit into
mainfrom
feat/meta-mfa-method-fields

Conversation

@lakhansamani

Copy link
Copy Markdown
Contributor

Adds the per-method MFA availability fields to the SDK's Meta type and getMetaData query, matching the server surface merged in authorizer#681, and bumps to 3.3.0-rc.1 for the RC that also carries passkey autofill (#43).

Added to Meta + getMetaData

  • is_totp_mfa_enabled
  • is_email_otp_mfa_enabled
  • is_sms_otp_mfa_enabled
  • is_webauthn_enabled

⚠️ Release coupling (CI note)

These fields exist only on an authorizer server ≥ today's main (added in #681). The integration test / CI pins AUTHORIZER_IMAGE=quay.io/authorizer/authorizer:2.3.0, which predates them — so the getMetaData integration test fails there with "Cannot query field is_totp_mfa_enabled". This is pure version skew; the change is correct against server main. CI goes green once a server RC image carrying #681 is published and AUTHORIZER_IMAGE is bumped to it. Unit tests + build + DTS typecheck pass.

Add is_totp_mfa_enabled / is_email_otp_mfa_enabled / is_sms_otp_mfa_enabled /
is_webauthn_enabled to the Meta type and the getMetaData query, matching the
server surface added in authorizer #681. Lets the login UI render per-method
MFA options. Bumps to 3.3.0-rc.1 for the RC that also carries passkey autofill
(#43).

Note: these fields require an authorizer server >= today's main; the pinned
integration-test image (2.3.0) predates them.
@lakhansamani lakhansamani merged commit 2b9f975 into main Jul 12, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant