Is JWT in Authorization header a standard? about django-rest-framework-jwt HOT 6 CLOSED

@pmcao definitely not a standard, but thanks for this question. We made the decision out of #4. The solution would probably be to make this header prefix configurable to anything, by default it'll probably be kept as JWT.

Thoughts?

from django-rest-framework-jwt.

Is there anyway to make the JWT string configurable? Other client side packages are sending Bearer instead of JWT.
Currently, satellizer (https://github.com/sahat/satellizer), a popular angularjs auth client, does not work with django-rest-framework-jwt because of this issue.

from django-rest-framework-jwt.

It's not difficult for me to make the Authorization header configurable, but this seems like an issue with django-rest-framework and/or django-rest-framework-jwt for not handling this case properly.

from django-rest-framework-jwt.

@sahat It's definitely an issue with this package. My proposal would be to make the header prefix configurable on django-rest-framework-jwt, by default it'll be kept as JWT. You'll be able to set it to Bearer.

from django-rest-framework-jwt.

Please refer to #32.

from django-rest-framework-jwt.

@pmcao @sahat just released a new version that includes a setting to override this. Let me know if you get a chance to test it out.

from django-rest-framework-jwt.