Skip to content

feat: add cross_app_access_requesting_app support for connections (EA)#1422

Open
ankita10119 wants to merge 3 commits into
masterfrom
DXCDT-1662
Open

feat: add cross_app_access_requesting_app support for connections (EA)#1422
ankita10119 wants to merge 3 commits into
masterfrom
DXCDT-1662

Conversation

@ankita10119

Copy link
Copy Markdown
Contributor

🔧 Changes

Adds schema support for the cross_app_access_requesting_app connection property introduced by the Cross App Access (CAA) feature.

What changed:

  • Added cross_app_access_requesting_app to the connections JSON schema src/tools/auth0/handlers/connections.ts. The field accepts { active: boolean } and follows the same pattern as the existing authentication and connected_accounts fields.

No additional handler logic was required, the property flows through the existing export and deploy paths automatically, as the auth0 Node SDK (^5.13.0) already includes the CrossAppAccessRequestingApp type on ConnectionForList.

Usage:

connections:
  - name: enterprise-oidc
    strategy: oidc
    cross_app_access_requesting_app:
      active: true

📚 References

🔬 Testing

Requires the token_vault_xaa feature flag enabled on the tenant.

Unit tests - added to test/tools/auth0/handlers/connections.tests.js:

  • Schema accepts cross_app_access_requesting_app with active: true/false
  • Schema rejects unknown properties (additionalProperties: false)
  • Property passes through unchanged in the connections.update payload

Manual end-to-end test (verified on dev-ankita-t.us.auth0.com with flag enabled):

  1. Exported tenant - cross_app_access_requesting_app absent from OIDC connection
  2. Added cross_app_access_requesting_app: active: true to the connection in tenant.yaml
  3. Deployed - API accepted the property, connection updated successfully
  4. Re-exported - cross_app_access_requesting_app: active: true present in exported YAML

Round-trip confirmed. Attempted deploy without the feature flag returns operation_not_supported (400) from the API - expected behavior, no special handling needed in the CLI.

📝 Checklist

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

@ankita10119
ankita10119 requested a review from a team as a code owner July 8, 2026 09:57
@codecov-commenter

codecov-commenter commented Jul 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.23%. Comparing base (0c9acc0) to head (3756532).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1422   +/-   ##
=======================================
  Coverage   80.23%   80.23%           
=======================================
  Files         163      163           
  Lines        7533     7533           
  Branches     1663     1663           
=======================================
  Hits         6044     6044           
  Misses        800      800           
  Partials      689      689           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

3 participants