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

How to restrict login options to "Apple Sign In" instead of showing form-based logins as well? #155

Open
derwaldgeist opened this issue Oct 6, 2022 · 2 comments

Comments

@derwaldgeist
Copy link

Our app uses multiple ways of authenticating a user, including login with username and password. Since some recent iOS update, everytime the Apple Sign In dialog pops up for a user that already had logged in with Apple before, Apple's login dialog shows all username/password options in addition to the actual Apple Sign In option. These login methods won't work, as there is no dialog to put a username and password in on our very first app screen. Is there a way to prevent iOS from showing these additional credentials, i.e. restrict the login options to Apple Sign In only?

@lupidan
Copy link
Owner

lupidan commented Dec 26, 2022

It may be that it's detecting a pair of User Id+Password inside the keychain for your particular app identifier, probably used in the past, or maybe in a website that shares your app ID or associated domain.

The "QuickLogin" (which at some point should be renamed to "CheckExistingCredentials" or something similar...) does check both SIWA, and keychain credentials, I believe that's why it shows both options in your particular case. I don't think it's related to the updated iOS version.

If you would like to strictly restrict it to SIWA, with the current code, I suggest you just call "LoginWithApple" and that's it.

@derwaldgeist
Copy link
Author

Thanks for the feedback! Just saw it, so sorry for the late response.

If I understand you correctly, "LoginWithApple" would work as a QuickLogin substitute?

Our app actually supports logins with username and password. If the QuickLogin supports this as well, is there a way to get that data and pass it to our login mechanism?

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

2 participants