Django REST framework oauth2

[pmcao]

Hi sahat,

Great work on satellizer so far. Should you consider integrating oauth2 of django REST server?
You will need to modify the parseUser function to extract the returned token.
In django REST server (and other oauth2 providers), the value of the returned token is in 'access_token' key instead of 'token' key as in your server examples.

Example of the django REST framework is available at this page:
http://www.django-rest-framework.org/api-guide/authentication#oauth2authentication

[sahat]

There should be a way to change the name of a token. I cannot change it in Satellizer just for Django REST Framework. But more importantly JSON Web Token is not exactly the same thing as access_token. If I call it access_token then it will create a lot of confusion with access_token from Facebook, Google, Twitter and other 3rd party providers.

[sahat]

@pmcao I am going to make the token name configurable as discussed in #50 so you could change it to access_token if you wish to.

[pmcao]

Thanks. I saw your commits.

Is there anyway to customize the Authorization header for an auth service? Can I use something else instead of "Bearer".
Some servers implementing JWT are accepting "Authorization: JWT " instead of "Authorization: Bearer "

If you could create an example of a client service for JWT, that would be great. I will be able to contribute an example of a server using django REST framework.

satellizer/satellizer.js

Line 612 in 5bb7194

httpConfig.headers.Authorization = 'Bearer ' + $window.localStorage[config.tokenName];

[sahat]

@pmcao I am going to close this issue. @jpadilla has opened a new issue in for django-rest-framework-jwt to get around this problem: jpadilla/django-rest-framework-jwt#32

[jpadilla]

@sahat thanks, I'll update both issues when it gets done, which should be soon this week.

[jpadilla]

As promised, https://github.com/GetBlimp/django-rest-framework-jwt/releases/tag/1.0.0