Add Configurable API Fetch Controls to Asgardeo SDK for Improved Performance

[dileepapeiris]

Purpose

This PR introduces granular configuration options to control automatic API calls made by the Asgardeo JavaScript SDK during the authentication flow, addressing performance concerns and providing developers with fine-grained control over network requests.

Problem:
Currently, the SDK automatically makes multiple API calls after successful sign-in:

• GET /scim2/Me - Fetches detailed user profile
• GET /scim2/Schemas - Fetches user attribute schemas
• GET /api/users/v1/me/organizations - Fetches user's associated organizations

These calls happen automatically even when applications don't need this data, impacting performance and increasing unnecessary network traffic.

Usage Example:

<AsgardeoProvider
  clientId="YOUR_CLIENT_ID"
  baseUrl="https://api.asgardeo.io/t/YOUR_ORG"
  preferences={{
    theme: {
      inheritFromBranding: false,  // Disable branding API
    },
    user: {
      fetchUserProfile: false,     // Disable SCIM2 calls
      fetchOrganizations: false,   // Disable organizations call
    },
  }}
>
  <App />
</AsgardeoProvider>

Related Issues

• Provide Configuration to Disable Unnecessary Authentication Network Calls #412

Related PRs

• N/A

Verification

Tested using the samples/teamspace-react app. Here is the screen recording.

Screen.Recording.2026-03-20.at.01.31.29.mov

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[asgardeo-github-bot]

🦋 Changeset detected

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.