[11.x] Auth Query optimization for api calls #1433
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While logging database queries I saw that there were 5 queries such as:
2 queries to
oauth_clients
table3 queries to
oauth_access_tokens
table (2 of which were made byleague/oauth2-server
package)In order to reduce number of queries some changes in code where made:
revoked
function in ClientRepository now will accept client as parameter instead of ID (this removes 1 query tooauth_clients
table). Client object that is passed to this function is returned from findActive function in ClientRepository. To fit those changes I have removed->with(1)
from clients mock in TokenGuardTests (revoked
).getPsrRequestViaBearerToken
function in TokenGuard that returns some result fromleague/oauth2-server
now will be passed as parameter tohasValidProvider
and from there toclient
function in TokenGuard (this process removes 1 query from 3 total queries made tooauth_access_tokens
table)Changes that were made in this pull request will remove 2 queries out of 5, bringing down number of total queries on each request from 5 to 3.