Closed tung2744 closed 4 months ago
- When transient token storage is used, I guess we should still persist the id Token and device secret in the persistence storage. Is this true?
It is not true in this pr. And I prefer not to modify it. I don't think there is any reason we need to persist device_secret and id_token now as native sso is not implemented yet.
- From your testing description, the testing steps may be too hard for other team members to follow. What about we introduce a new section for app-initiated sso to web? The goal is that we do not need to change the client ID input field or change token storage to transient. Instead, we ask the user to input a client ID (which can be optional, default to the current one), and a redirect URI (optional, default to the current one). We also should not ask the user to turn on browser SSO. We should create a new container with a random different name each time, with transient token storage, with browser SSO turned on. What do you think?
I think I can create a new issue to make the example app easier to use.
Renamed SharedStorage to InterAppSharedStorage.
Also fixed a bug that state
is not passed to server.
ref DEV-1407
How to test
client1id
client2id
. Setx_app_initiated_sso_to_web_enabled
to true for both clients.client1id
as the "Client ID". Fillclient2id
as the "App Initiated SSO To Web Client ID". Check "Is App Initiated SSO To Web Enabled". Press configure.