You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your suggestion related to an experience ? Please describe.
In Choreo, we use the org creation endpoint from Asgardeo, which requires to call with Asgardeo token. But in a logged in session, we only have the STS token, hence we trigger silent signin request to get the Asgardeo token again. However recently there's an issue in silent signin for low privileged users occurred. Hence we are unable to create new organizations.
As a workaround to this problem, we propose the capability to store both Asgardeo & STS token in the SDK, so that we can retrieve the Asgardeo token from SDK itself, and call the Asgardeo org creation endpoint.
Describe the improvement
Support the capability to store both Asgardeo & STS token in the SDK, so that Choreo can use it.
Additional context
The text was updated successfully, but these errors were encountered:
Is your suggestion related to an experience ? Please describe.
In Choreo, we use the org creation endpoint from Asgardeo, which requires to call with Asgardeo token. But in a logged in session, we only have the STS token, hence we trigger silent signin request to get the Asgardeo token again. However recently there's an issue in silent signin for low privileged users occurred. Hence we are unable to create new organizations.
As a workaround to this problem, we propose the capability to store both Asgardeo & STS token in the SDK, so that we can retrieve the Asgardeo token from SDK itself, and call the Asgardeo org creation endpoint.
Describe the improvement
Support the capability to store both Asgardeo & STS token in the SDK, so that Choreo can use it.
Additional context
The text was updated successfully, but these errors were encountered: