Skip to content
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

Add access token instance as a request field #133

Open
masci opened this issue Jun 25, 2014 · 4 comments
Open

Add access token instance as a request field #133

masci opened this issue Jun 25, 2014 · 4 comments

Comments

@masci
Copy link
Contributor

masci commented Jun 25, 2014

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.

@AduchiMergen
Copy link

👍

@fboerman
Copy link

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

@IvanAnishchuk
Copy link
Member

I'm looking at this and would like to check whether those fields are accessible and provide the info in discussion...

@auvipy
Copy link
Contributor

auvipy commented Oct 26, 2021

I'm looking at this and would like to check whether those fields are accessible and provide the info in discussion...

can you give that a try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants