Update Asgardeo V2 to use authId
#278
Merged
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.
This pull request updates the authentication flow in both the API and React client to use
authIdinstead ofsessionDataKeyfor tracking authentication sessions in Asgardeo V2. The change standardizes the identifier used across API requests, React components, and session storage, improving consistency and clarity throughout the codebase.Authentication Identifier Migration:
sessionDataKeywithauthIdin the API functionsexecuteEmbeddedSignInFlowV2andexecuteEmbeddedSignUpFlowV2, including request payloads and conditional logic. [1] [2] [3] [4] [5] [6]EmbeddedFlowExecuteRequestConfigV2interface in both sign-in and sign-up models to use an optionalauthIdproperty instead ofsessionDataKey. [1] [2]React Client and Component Updates:
AsgardeoReactClient.ts) to retrieve, store, and passauthIdfrom URL parameters and session storage, replacing all references tosessionDataKey.SignIncomponent to handleauthIdinstead ofsessionDataKeyin URL parsing, session storage operations, and flow cleanup logic, ensuring the new identifier is used throughout the sign-in flow. [1] [2] [3] [4] [5] [6] [7]Related PR