This release is a pre-release and may not be stable for production use.
Access your Plone RSS feeds as authenticated user.
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 every times he wants in his personal preferences. This token is part of the query string of the authenticated RSS field, 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
Plone 4.1 only as this component is still a baby. Plone 4.0 support should not be that difficult (contributors are welcome).
Installation
Production site
As usual in your zc.buildout configuration:
[instance]
recipe = plone.recipe.zope2instance
...
eggs =
aws.authrss
Development site
Developers of aws.authrss should use this:
[instance]
recipe = plone.recipe.zope2instance
...
eggs =
aws.authrss[test]
Upgrading
Available upgrades may be executed from the portal_setup tool of your Plone site in the Upgrades tab.
Customization
aws.authrss comes with its own tokens manager that stores tokens in an OOBtree. See the module 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
- At the cheeseshop
Planned features
Provide the same authenticated RSS feeds to search results but this requires to override the standard search template machinery, and I hate overriding templates. Patches are welcome.
Do not assign tokens to users authenticated from an user folder that’s not in the Plone site.
Add unit tests to KSS handlers (Any help appreciated).
Contributors
Gilles Lenfant: Main developer and french translation
Changelog
1.0.0a2
Fixed packaging issues. [glenfant]
1.0.0a1
First public version [glenfant]
Metadata
Release files for aws.authrss 1.0.0a2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws.authrss-1.0.0a2.tar.gz | 19.9 kB | Without provenance | Details for aws.authrss-1.0.0a2.tar.gz |
Release files / aws.authrss-1.0.0a2.tar.gz
| Download URL | aws.authrss-1.0.0a2.tar.gz |
|---|---|
| Size | 19.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
288960aefbd9fdcc3b4e16e1ba333b57b7f32dcc45b38b9dddc99c6682bb3162
|
|
BLAKE2b-256 checksum How to use checksums |
64cfa5ede70bceade7878536dc2cbbf4bbd7ed6d93b49e85488a509ce567cb3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for aws.authrss 1.0.0a2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.