Re: [Mailman-Developers] How to set up mailman 3
On Mar 30, 2017, at 09:45 PM, Jan Jancar wrote:
>This would also go well with an idea I had about the current state of
>the REST API and encrypted lists. With having decorators like
>"@exported_REST", another one could get introduced, something like
>"@requires_permission("some.perm.name")" which would introduce
>permission-based granularity to the REST API. Then multiple
>user:password pairs could be specified in a config with different
>permissions and so Mailman could provide different levels of API access
>to different apps.
Our intention is to support permission based access to the REST API via an
"authenticating proxy", which we call lemme:
https://gitlab.com/mailman/lemme/tree/master
and for an outline on how this might work:
https://gitlab.com/mailman/lemme/blob/master/OUTLINE.rst
We had good discussions about this at Pycon 2016, but haven't gotten very far
in implementation details. I'm hoping we can spend a little bit of time on
that this year.
Cheers,
-Barry
pgpYeAo5cY8pt.pgp
Description: OpenPGP digital signature
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] How to set up mailman 3
On Mar 31, 2017, at 03:01 AM, Stephen J. Turnbull wrote: >That sounds cool, but I tend to feel that WADL gets pretty heavy. If >we can't just mark things with something like "@exported_REST", it's >not clear that the maintenance burden is worth it. Agreed, but note this is only one half of the equation. You also need to publish the static definition of the REST API so that HTTP clients could discover it. That's my understanding of the role that WADL serves. Cheers, -Barry pgpwaeFD0FVWY.pgp Description: OpenPGP digital signature ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] How to set up mailman 3
On 03/30/2017 08:01 PM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
> > up on the state of the art, but IIRC, there were Python libraries that
> could
> > generate bindings based on WADL.
>
> That sounds cool, but I tend to feel that WADL gets pretty heavy. If
> we can't just mark things with something like "@exported_REST", it's
> not clear that the maintenance burden is worth it.
This would also go well with an idea I had about the current state of
the REST API and encrypted lists. With having decorators like
"@exported_REST", another one could get introduced, something like
"@requires_permission("some.perm.name")" which would introduce
permission-based granularity to the REST API. Then multiple
user:password pairs could be specified in a config with different
permissions and so Mailman could provide different levels of API access
to different apps.
Although, reading Barry's message again, this may not be possible /
maintainable.
-Jan
signature.asc
Description: OpenPGP digital signature
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] How to set up mailman 3
Barry Warsaw writes: > up on the state of the art, but IIRC, there were Python libraries that could > generate bindings based on WADL. That sounds cool, but I tend to feel that WADL gets pretty heavy. If we can't just mark things with something like "@exported_REST", it's not clear that the maintenance burden is worth it. Steve ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] How to set up mailman 3
On Mar 30, 2017, at 12:57 PM, Stephen J. Turnbull wrote: >Would you recommend against even exploring for a lightweight approach >for some reason? Ie, the idea is bad according to some principle? To the contrary, I think if it were possible it would be pretty nice. In fact, you could conceivably eliminate mailman-client if you could do it, and other languages could auto-generate bindings to the REST API. I haven't kept up on the state of the art, but IIRC, there were Python libraries that could generate bindings based on WADL. Cheers, -Barry pgpWUNDtMcI44.pgp Description: OpenPGP digital signature ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
