-
Notifications
You must be signed in to change notification settings - Fork 562
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
(expo/use-sso) Add redirectUrl
parameter to startSSOFlow
; remove expo partials
#2005
base: main
Are you sure you want to change the base?
Conversation
Hey, here’s your docs preview: https://clerk.com/docs/pr/2005 |
e09d8b5
to
ef80482
Compare
Blocked until clerk/javascript#5127 gets merged |
redirectUrl
parameter to startSSOFlow
redirectUrl
parameter to startSSOFlow
; remove expo partials
const { createdSessionId, setActive, signIn, signUp } = await startSSOFlow({ | ||
strategy: 'enterprise_sso', | ||
identifier: email, | ||
redirectUrl: '/', // The URL to redirect to after successful authentication |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is optional, by default it's sso-callback
, I think we should update the useSSO
reference
It shouldn't be a raw string - it's on the type level, but you'd call some Expo API to generate the URL based on the platform: Native would use a deep link scheme vs a web URL
The commit to add |
5218396
to
fbf01cb
Compare
Changed got release, therefore this PR is unblocked |
@LauraBeatris I'm not sure how to do linking with expo. I did |
- `redirectUrl?` | ||
- `string` | ||
|
||
The full URL or path to redirect to after the SSO flow is complete. If not specified, defaults to `sso-callback` path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If not specified, defaults to
sso-callback
path.
But I don't see where the /sso-callback
is used - users don't have to set anything up for this page, so if this /sso-callback
path is actually hit behind the scenes, is this even worth mentioning?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If deep linking is working - in this case, for Android since iOS currently has a bug from our tests so far (expo/expo#34187)
And redirectUrl
is not defined, then we'll navigate to sso-callback
, and if they don't have this route configured on the app, it'll lead to a 404 - reason why I think it's worth mentioning the default
🔎 Previews:
What does this solve?
Adds a new
redirectUrl
parameter tostartSSOFlow
Checklist