Thank you everyone for your feedback. A working proposal for authentication is available on the development email list, so please feel free to join the discussion there.
https://www.redhat.com/archives/pulp-dev/2016-September/msg00049.html Michael On Mon, Aug 29, 2016 at 9:20 AM, Russell E. Glaue <rgl...@cait.org> wrote: > We use the current two authentication methods. > > 1. We use cert-based auth for connections from our continuous integration > environment, managed by Jenkins. > 2. We also use the basic auth for connections to the REST API. > > We'd love to have something more REST friendly, like JSON Web Tokens > (JWT), that we can use in place of Basic Auth. > https://jwt.io/ > > Though we do like and want to keep Basic Auth too, for some one-off tasks. > > > Is the community considering to use the Django REST framework? > http://www.django-rest-framework.org/ > It supports Oauth.... but it would be great to have the JWT support! > https://github.com/GetBlimp/django-rest-framework-jwt > > > -RG > > > ----- Original Message ----- > From: "Aurélien DESBRIÈRES" <aurelien.desbrie...@gmail.com> > To: "Konstantin M. Khankin" <khankin.konstan...@gmail.com>, "Michael > Hrivnak" <mhriv...@redhat.com> > Cc: "pulp-list" <pulp-list@redhat.com> > Sent: Sunday, August 28, 2016 6:53:51 AM > Subject: Re: [Pulp-list] Feedback needed: new user/auth system in 3.0 > > > > > Hum ... Hope I will have not to rebuild all once again. > > > On Sun, Aug 28, 2016, 12:41 PM Konstantin M. Khankin < > khankin.konstan...@gmail.com > wrote: > > > > I use PAM auth, which is in turn authenticates login requests through > FreeIPA. I don't create any roles other than admin though > > > > 2016-07-15 22:29 GMT+03:00 Michael Hrivnak < mhriv...@redhat.com > : > > > > As many of you know, we are switching from mongodb to postgres in Pulp > 3.0. This will come with quite a few changes. For one in particular, we > need your input about how you use Pulp's user and permission system. > Anything you can tell us about how you use the current user/perm system > would be very helpful. We are considering the use of Django's built-in > user/auth system [0] as a replacement for what Pulp currently has. > > > If we hear silence, we might be more likely to change things, so let us > know what is important to you. > > > > > Have you integrated Pulp with a separate authentication source? Which one? > > > Do you assign permissions to specific users? How granular do you need that > to be? > > > Have you created "roles" in Pulp? > > > Anything else you want us to know or to think about? > > > If you would like to provide input confidentially, you are welcome to > contact me directly. > > > [0] https://docs.djangoproject.com/en/1.8/topics/auth/ > > > Thank you! > Michael > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list > > > > > > -- > > Ханкин Константин > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
