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

clientId not set? #99

Open
kennardconsulting opened this issue Aug 11, 2023 · 2 comments
Open

clientId not set? #99

kennardconsulting opened this issue Aug 11, 2023 · 2 comments

Comments

@kennardconsulting
Copy link

First, thanks for this great plugin! I am using it on both Web and iOS.

Everything works great on Web. It almost works on iOS, but the error I get when trying to make use of the returned identityToken is "client_id mismatch. The code was not issued to xxx.xxx"

Debugging inside Plugin.swift, I can see that the call object has call.options["clientId"] set correctly to my app's client_id. However I cannot see anywhere that Plugin.swift makes use of this value? It doesn't seem to set it on the request that gets sent to Apple?

@kennardconsulting
Copy link
Author

kennardconsulting commented Aug 11, 2023

Possibly I'm mistaken and a native app will always just send its own appId as the clientId, with no ability to override this in the Apple authentication API? So clientId is only relevant for Web?

@kennardconsulting
Copy link
Author

Confirmed. It's working if I use my native appId when making use of the returned identityToken. However, it would be nice if there was a way to override clientId so that my Web UI and native UI are sending identityTokens generated using the same clientId (that way my back-end doesn't have to differentiate).

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

1 participant