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
At the moment, when using DRF the access token instance is added to the request object and users have access to the application instance and the client_id through: request.auth.application.client_id.
The same doesn't happen when users don't use DRF, and all that they have in the request object is the resource_owner field.
A token field should be added to request objects so that users can access application instance and then the client_id through request.token.application.client_id both when using DOT mixins for CBVs and DOT decorators for function based views.
The text was updated successfully, but these errors were encountered:
so this is a long no updated issue but I was wondering if there was any progress on it? It would be really handy to have. Is there a workaround available? I was thinking about simply lifting the token from request.META
At the moment, when using DRF the access token instance is added to the request object and users have access to the application instance and the client_id through:
request.auth.application.client_id
.The same doesn't happen when users don't use DRF, and all that they have in the request object is the
resource_owner
field.A
token
field should be added to request objects so that users can access application instance and then the client_id throughrequest.token.application.client_id
both when using DOT mixins for CBVs and DOT decorators for function based views.The text was updated successfully, but these errors were encountered: