[Pulp-dev] Pulp3 - JWT Authorization Header

[David Davis]

There was some discussion on the PR about this:

https://github.com/pulp/pulp/pull/3109#discussion_r138202256

Basically the package we’re using decided on JWT. See their reasoning here:

https://github.com/GetBlimp/django-rest-framework-jwt/pull/4


David

On Fri, Oct 27, 2017 at 8:26 AM, Kersom Moura Oliveira <kersom at redhat.com>
wrote:

> Hi,
>
> I noticed that JWT authorization header was adopted as the default one for
> Pulp3. [0]
>
> Also I read in a few places about Bearer authorization header,  as the
> typical one used for JWT.[1]
>
> Is there a specific reason to chose one over the other in Pulp3?
>
> Regards,
>
> [0] https://docs.pulpproject.org/en/3.0/nightly/integration_
> guide/rest_api/authentication.html#using-a-token
> [1] https://jwt.io/introduction/
> [2] https://tools.ietf.org/html/rfc6750
> [3 ]https://tools.ietf.org/html/rfc7523
>
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20171027/c1545908/attachment.htm>