Private Plone RSS feeds through a user private token
Project description
Access your Plone RSS feeds as authenticated user. This feature was inspired by Redmine.
Abstract
Actually, authenticated users in Plone site may read content that are not available to anonymous users. But when subscribing to a Plone RSS feed they can only view items that are available to anonymous users. Just because the RSS readers such as Google Reader do not - and cannot - provide feature to provide authentication cookie or header to authenticate on the feed URL.
aws.authrss gives to the authenticated users a dedicated and private link to the Plone RSS feeds. Such feeds provide all elements the user is entitled to view, when authenticated in the Plone site with a browser, and of course, relevant to the feed (Folder, Collection, …)
Each user may have a private token he can change whenever he wants in his personal preferences. This token is part of the query string of the authenticated RSS feed, and identifies the user only for the RSS feeds.
A control panel for site administrators gives the possibility to prune private tokens of removed users.
Plays with
The module supports Plone 4.3 and 5.0.
Installation
Production site
As usual in your zc.buildout configuration:
[instance]
recipe = plone.recipe.zope2instance
...
eggs =
aws.authrss
Development site
The development package at Github comes with a suitable buildout.cfg. See Links. You just need to clone that repository and play the usual python bootstrap.py + bin/buildout.
In Site Setup
Don’t forget to enable syndication in the Syndication control panel and to check the Show feed link checkbox.
Upgrading
Available upgrades may be executed from the portal_setup tool of your Plone site in the Upgrades tab.
Customization
Integrators
aws.authrss overrides the portal_actions/document_actions/rss action to add the authenticated RSS link in your site.
Developers
aws.authrss comes with its own tokens manager that stores tokens in an OOBtree. See the class aws.authrss.tokenmanager.DefaultTokenManager.
You may provide your own tokens manager registering an utility that implements aws.authrss.interfaces.ITokenManager in your component’s override.zcml. Then install this local utility using a GenericSetup componentregistry.xml file like this one:
<?xml version="1.0"?>
<componentregistry>
<utilities>
<utility
interface="aws.authrss.interfaces.ITokenManager"
factory="my.component.tokenmanager.DefaultTokenManager"
/>
</utilities>
</componentregistry>
Credits
This Plone component is sponsored by Alter Way
Links
- At github.com (contributors)
- At pypi (integrators)
Planned features
Do not assign tokens to users authenticated from an user folder that’s not in the Plone site (i.e a Zope root manager).
Contributors
Gilles Lenfant: Main developer and french
Vincent Fretin: Update to Plone 4.3 and 5.0
Changelog
2.0.1 (2016-11-28)
Update github link to point to collective. [vincentfretin]
2.0.0 (2016-11-26)
Drop support for Plone < 4.3 and Python 2.6. Add compatibility for Plone 4.3 and 5.0 on Python 2.7. [vincentfretin]
1.0.0b2
Fixed packaging issue with MANIFEST.in [glenfant]
1.0.0b1
Added support for search results [glenfant]
1.0.0a2
Fixed packaging issues. [glenfant]
1.0.0a1
First public version [glenfant]
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
