feat: add Network ACL Keys, 3P client access, and XAA connection profile support - #1391
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1391 +/- ##
========================================
Coverage 89.72% 89.73%
========================================
Files 439 441 +2
Lines 20668 20799 +131
Branches 9742 9809 +67
========================================
+ Hits 18544 18663 +119
- Misses 2124 2136 +12
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Generated by Fern CLI Version: unknown Generators: - fernapi/fern-typescript-sdk: 3.72.5
Patches applied (3): - patch-066ff9e0: docs: add v6 migration guide for breaking changes in v6.0.0 (#1368) - patch-d8faf7a2: docs: update v6 migration guide with federatedConnectionsTokensets and federated_connections_access_tokens breaking changes (#1370) - patch-0f7baa6f: fix: auto-stamp SDK_VERSION from package.json during build (#1382) Patches with unresolved conflicts (3): - patch-490e5634: feat(management): add sub-package exports and management auth helper (#1373) - patch-74170bb0: Release v6.1.0 (#1381) - patch-4fcb39a4: Release v6.2.0 (#1389) Run `fern-replay resolve` to apply these customizations.
fern-api
Bot
force-pushed
the
fern-bot/2026-08-18_05-58-19_128
branch
from
August 18, 2026 10:54
81454f5 to
f393756
Compare
ankita10119
approved these changes
Aug 18, 2026
developerkunal
approved these changes
Aug 19, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Automated SDK regeneration adding support for Network ACL Keys management, Third-Party (3P) Client Access configuration for Organizations, and Cross-App Access (XAA) resource app configuration for Connection Profiles.
Changes
Network ACL Keys
keys.networkAclssub-resource: list, create, get/keys/network-acls- retrieve all keys, ordered by creation time descending/keys/network-acls- create a new key/keys/network-acls/{id}- retrieve a specific keyNetworkAclKey,NetworkAclKeyAlgorithmEnumtypes (currently only hmac-sha256 supported)read:network_acl_keysandcreate:network_acl_keysOAuth scopesmatch_all?: booleantoNetworkAclRule- when true, unconditionally matches all traffic regardless of other signals; mutually exclusive with match and not_matchThird-Party (3P) Client Access - Organizations (EA)
my_organization_configuration.third_party_client_accesstoPOST/GET/PATCH /api/v2/clientsrequests and responses{ default_value: "block", allowed_values: ("block" | "allow")[] }Cross-App Access (XAA) - Connection Profiles (EA)
cross_app_access_resource_apptoPOST/GET/PATCH /api/v2/connection-profilesrequests and responses{ status: { default_value: "enabled" | "disabled", allowed_values: ("enabled" | "disabled")[] } }Connection Options
useOauthSpecScope?: booleanto OIDC connection options - uses space-delimited scopes per OAuth 2.0 spec instead of comma-delimited when calling the IdP's authorization endpointError Handling Improvements
flows.update()andforms.update()Documentation Fixes
custom_login_page_off→custom_login_page_onin JSDoc forclients.create()andclients.update()- the field was nevercustom_login_page_off, corrected to the actual Auth0 API field nameconnections.update()docs: "If any options are unspecified, the default will be used, even if it differs from the existing value"Type Corrections
Fields on tokens, sessions, custom domains, forms, and self-service profiles that were typed as T | undefined are now correctly typed as (T | null) | undefined to accurately reflect what the API already returns at runtime. No runtime behavior change.
Affected types:
GetRefreshTokenResponseContent,RefreshTokenResponseContent,UpdateRefreshTokenResponseContent-created_at,idle_expires_at,expires_at,last_exchanged_atGetSessionResponseContent,SessionResponseContent,UpdateSessionResponseContent-created_at,updated_at,authenticated_at,idle_expires_at,expires_at,last_interacted_atSessionAuthenticationSignal-timestampUpdateFormRequestContent-messages,languages,translations,nodes,start,ending,styleUpdateSelfServiceProfileRequestContent-brandingUpdateUserAttributeProfileRequestContent-user_idFlowActionFlowMapValueParams-fallbackTesting
keys/networkAcls(365 lines) andflows/executions(38 lines)flows,forms, andnetworkAclswith new error case coverageChecklist