-
Notifications
You must be signed in to change notification settings - Fork 12
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
Auth UI #411
Auth UI #411
Conversation
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.
Thanks! Initial feedback.
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.
A few questions / thought / clarifications
a3a9625
to
f1beac8
Compare
I have rewritten this PR. Various specs have been updated to reflect the new design. |
|
||
### Custom domain | ||
|
||
If the app is using custom domain, then Auth Gear is served at the developer's wish. |
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.
No sure how custom domain looks like after this change? Originally we only have one domain for all gears and Skygear App.
After auth ui is supported, developers can configure gears domain and skygear app domain separately?
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.
Yes. I should update the spec of custom domain to reflect this.
|
||
## Old SDK and old gateway behavior | ||
|
||
When the SDK receives a response with `x-skygear-try-refresh-token: true`, it tries to refresh the access token. |
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.
We can try using silent authentication.
- Login at authorize, set cookie at AuthUI
- On app launch/expired -> call authorize with prompt = none
- AuthUI check cookie session: yes -> return code, no -> return 401
- Receive code & send token request, receive access_token + expires_in, NO REFRESH TOKEN
- When expires (according to expires_in): go to 1
- When receive 401: either revoked, or custom 401 -> goto 1
- "https://example.com" | ||
client_name: Web App | ||
logo_uri: "https://example.com/logo.png" | ||
disabled: false |
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.
remove this, spec is not updated.
ref #370
ref #382
Rendered document