https://supertokens.com/
Join Discord
Hi guys, I'm a bit lost with adding Apple signinup support. As mentioned in the docs, Apple requires...
# support-questions-legacy
v
Hi guys, I'm a bit lost with adding Apple signinup support. As mentioned in the docs, Apple requires different client_id for every client. We have 3 frontends (4 if you consider android). So 4 client ids. As I understood every frontend should send it's own client_id to the server and I see that /signinup endpoint supports it. But what about /authorisationurl endpoint? It only accepts provider name, there is no way to pass client id there. So as a result you always get default client id back in response and redirect to Apple sign in page breaks of course. What am I missing?
I also see that findRightProvider function has clientId set to undefined for this route handler. So I suppose it's by design. What am I doing wrong? https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/api/authorisationUrl.ts#L39
r
Hey @vyobukhov the 
/authorisationurl
API is only required for web based login, and you should only require one client ID for websites. For mobile apps, this API is not needed.
v
Thx, so for all the web clients I should use a single client id
r
yes
v
Thank you
r
st-bot-test-case
PreviousNext
Powered by

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by