Implement multi organization context management support

[kavindadimuthu]

Purpose

This pull request introduces multi-organization authentication context support, enabling users to authenticate and exchange tokens across different organization contexts. The main changes include improvements in session and storage management keyed by instance, and new configuration options and React components for organization chaining.

Multi-organization context and token exchange support:

• Added organizationChain configuration to both BaseConfig and DefaultAuthClientConfig, allowing specification of sourceInstanceId and targetOrganizationId for chained authentication and token exchange between organizations. [1] [2]
• Updated the exchangeToken and replaceCustomGrantTemplateTags logic to fetch session data from the appropriate organization context, using the organizationChain configuration to determine the correct instance for access tokens. [1] [2] [3] [4]

Session and storage management improvements:

• Enhanced StorageManager to support resolving keys and retrieving session data based on both userId and instanceId, ensuring correct data isolation between organization contexts. [1] [2]

React SDK enhancements:

• Added a new OrganizationContext React component to encapsulate organization context configuration and propagate it through the component tree, supporting nested/multi-organization scenarios.
• Updated AsgardeoReactClient.switchOrganization to utilize the new organizationChain configuration and determine if sign-in is required based on the presence of a sourceInstanceId. [1] [2]

These changes collectively enable seamless authentication flows across multiple organizations, improve isolation of authentication state, and provide a more robust foundation for multi-tenant applications.

Related Issues

• N/A

Related PRs

• N/A

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests 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]

⚠️ No Changeset found

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go.

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.