You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nomenclature in referencing access tokens in Netlify functions using Netlify identity is a bit different.
Netlify attaches a clientContext property to the Netlify Function context instead of an identityContext. Additionally, Netlify attaches a user property to the clientContext vs a claims object.
Would it be worth updating the properties in the @serverless-jwt/netlify package to match? This way validation will occur in the same way regardless of where the tokens come from.
In summary...
identityContext becomes clientContext
claims becomes user
The text was updated successfully, but these errors were encountered:
The nomenclature in referencing access tokens in Netlify functions using Netlify identity is a bit different.
Netlify attaches a
clientContext
property to the Netlify Functioncontext
instead of anidentityContext
. Additionally, Netlify attaches auser
property to theclientContext
vs aclaims
object.Would it be worth updating the properties in the @serverless-jwt/netlify package to match? This way validation will occur in the same way regardless of where the tokens come from.
In summary...
identityContext
becomesclientContext
claims
becomesuser
The text was updated successfully, but these errors were encountered: