-
Notifications
You must be signed in to change notification settings - Fork 0
feat: decode user data from JWT access token and add impersonated property #32
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
Conversation
dd276d9 to
811f303
Compare
811f303 to
4e24dcb
Compare
4e24dcb to
87e3f5d
Compare
ondrejsevcik
left a comment
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.
LGTM 👍🏼 Only a few cosmetic issues.
| name: z.string(), | ||
| profilePictureUrl: z.string().nullable().optional(), | ||
| tenantId: z.string(), | ||
| act: z |
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.
🟢 It would be good to add some link to Frontegg docs for this variable. For someone like me (who sees this first time), it would be very helpful.
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.
Unfortunately there are none.
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
AP-5345
Instead of making another GET request to
/frontegg/identity/resources/users/v2/mewe can decode the same information from the JWT access token that we already received from thesilentortokenendpoints.This PR also adds an
impersonated: booleanproperty to the user data response to determine whether the current session is impersonated.