[fern-api]

Changes

SDK regeneration from the Auth0 OpenAPI spec via Fern. Adds user consent signing keys, OTP settings for database connections, a type on resource servers, and a tenant_domain option on the Management client, along with response-side OIDC support on clients and new fields on SAML connections, event stream contexts, and experiment segments. Removes the captcha_policies sub-client from attack protection.

🆕 New endpoints / types:

• Consent Signing Keys - new list_consent_signing_keys, get_consent_signing_key, and delete_consent_signing_key on client.users, calling users/{id}/consent-signing-keys and users/{id}/consent-signing-keys/{kid}, backed by ConsentSigningKey (kid, device_identifier, created_at, expires_at) and ListUserConsentSigningKeysResponseContent
• Management tenant domain - new tenant_domain option on Auth0::Management.new that builds the base URL as https://<tenant_domain>/api/v2 when base_url is not set

✏️ Modified endpoints (new properties):

• Connection OTP settings - otp_settings on database connection create, update, and response types, backed by new ConnectionOtpSettings (email, phone) and ConnectionOtpChannelSettings (otp_length, otp_expiry)
• Client OIDC support on responses - oidc_support on the Client type and on the client get, create, update, rotate secret, and search responses, backed by new ClientOidcSupport (is_allowed, allow_all_scopes, allowed_scopes)
• Resource server type - type on resource server create and update requests and on resource server get, create, update, and search responses, backed by new ResourceServerTypeEnum (universal_commerce_protocol_server)
• SAML Cross App Access requesting app - cross_app_access_requesting_app on SAML connection create, update, and response types, with new ConnectionClientIDSamlxaaRequestingApp and ConnectionClientSecretSamlxaaRequestingApp aliases
• SAML client credentials - client_id and client_secret on ConnectionOptionsSaml
• Segment status filter - status (SegmentStatusEnum) on experimentation.segments.list
• Passkey Guardian factor - passkey added to GuardianFactorNameEnum
• Event stream transaction context - transaction on EventStreamCloudEventContext, backed by new EventStreamCloudEventContextTransaction and the EventStreamCloudEventContextTransactionProtocolEnum, EventStreamCloudEventContextTransactionResponseModeEnum, and EventStreamCloudEventContextTransactionResponseTypeItemEnum enums

⚠️ Breaking Changes:

• client.attack_protection.captcha_policies removed - the captcha_policies sub-client (list, create, get, delete, update on attack-protection/captcha/policies) is removed, along with AttackProtectionCaptchaPolicy, AttackProtectionCaptchaPolicyAction, AttackProtectionCaptchaPolicyMatch, CaptchaActiveProviderEnum, the per-provider CaptchaPolicyAction* types, ListAttackProtectionCaptchaPoliciesResponseContent, and the create and update request content types. Migration: none, as the SDK no longer exposes captcha policy endpoints.
• allocation_strategy required on experiment create - allocation_strategy on CreateExperimentRequestContent is now required instead of optional. Migration: pass allocation_strategy (percentage or segment) when calling client.experimentation.experiments.create.

Testing

Wire tests were regenerated for the new consent signing key endpoints and the experiment changes, and the captcha policies wire test was removed with the sub-client. The unit tests pass, and the live-tenant integration test passes against a dev tenant.

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of Ruby

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All existing and new tests complete without errors
• Rubocop passes on all added/modified files
• All active GitHub checks have passed

[kishore7snehil]

LGTM!