-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Updated frame.context to use req.api_key #9965
Conversation
core/server/api/shared/http.js
Outdated
user: ((req.user && req.user.id) || (req.user && models.User.isExternalUser(req.user.id))) ? req.user.id : null, | ||
client: (req.client && req.client.slug) ? req.client.slug : null, | ||
client_id: (req.client && req.client.id) ? req.client.id : null | ||
api_key: (req.api_key && req.api_key.id) ? req.api_key.id : null, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
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.
FFTSM 👍
refs #9865
This is split out from #9869 to make it easier to review
It adds the id of
req.api_key
, if it exists to the context object. This is necessary so that controllers can verify permissions of api_keys.It also removes the client and client_id parts of the context object - as they are not used past v0.1