Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Will it support authing for other type of apps, eg, android/ios? #332

Open
neeboo opened this issue Jun 12, 2021 · 2 comments
Open

Will it support authing for other type of apps, eg, android/ios? #332

neeboo opened this issue Jun 12, 2021 · 2 comments

Comments

@neeboo
Copy link

neeboo commented Jun 12, 2021

We are currently making the flutter agent for IC,soon there will be devs to build other types of client.

I'm thinking to build a auth-client package for flutter, which will works similar to the javascript package.

However there are some differences between web app authing and native app authing.

  1. To use current browser's Webauthn feature, the native side will open browser window or shared modal.
  2. To the auth-client of js, it use window.postMessage to pass the request payload to the Auth page. But native does not, so we are thinking to pass the URLParameters to it.
  3. So the Identity WebApp will find a way to extract the query info, then pass the login process.
  4. Then after login success or fail, the Identity WebApp will use window.location.href={scheme}://{callback_path}?success={true|false}&payload={payload} to pass the response with delegations back to the native which will use auth-client to receive.

That may require some changes and any good idea we can discuss about?

@ehsan6sha
Copy link

ehsan6sha commented Jul 9, 2021

We are currently making the flutter agent for IC,soon there will be devs to build other types of client.

I'm thinking to build a auth-client package for flutter, which will works similar to the javascript package.

However there are some differences between web app authing and native app authing.

  1. To use current browser's Webauthn feature, the native side will open browser window or shared modal.
  2. To the auth-client of js, it use window.postMessage to pass the request payload to the Auth page. But native does not, so we are thinking to pass the URLParameters to it.
  3. So the Identity WebApp will find a way to extract the query info, then pass the login process.
  4. Then after login success or fail, the Identity WebApp will use window.location.href={scheme}://{callback_path}?success={true|false}&payload={payload} to pass the response with delegations back to the native which will use auth-client to receive.

That may require some changes and any good idea we can discuss about?

Did you completed this? I am building a react-native and would like your insights if possible.
I tried using WebView which was unable to load Internet Identity. In other options we do nto have access to postMessage that II is currently using

@krpeacock
Copy link
Contributor

We had URLParameters as an option in the initial design of II, and I think that supporting OAUTH flows is still a valid path that we should pursue. Security nixed it originally, but I think if Google and Facebook can support it, so can we.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants