This is a fork of collective.login_monitor. It adds reliable postgresql support (we could only get sqlite working with it). We don't promise compatibility between collective.login_logger and collective.login_monitor. We Save any login operation done in your Plone site to an external database and provide a Plone interface to query the database.
Table of contents
This Plone add-on is based on z3c.saconfig and SQLAlchemy, and can't provide any new feature to Plone without a proper configuration.
Keep reading for installation and configuration guide.
After the installation, any login done in your Plone will save to an external database an entry that store:
- user id
- a timestamp
Then a new configuration panel can bhe found in the site configuration: "Log user logins".
From this view you can query the database previously populated:
You must limit the search inside a rande of dates, and optionally limiting users to members of a group. Results of the table displayed can be export to a CSV file.
If your buildout hosts multiple Plone sites, all of them will store data in the database keeping same username on different sites separated.
You must configure an access to an external DBMS. The name of the engine used must be plone_logins.
Follow an example based on sqlite (not advised for production environment).
Add collective.login_logger to your buildout, then provide a SQLAlchemy connection string:
[buildout]
...
[instance]
...
eggs=
...
collective.login_logger
zcml-additional =
...
<configure xmlns="http://namespaces.zope.org/zope"
xmlns:db="http://namespaces.zope.org/db">
<include package="z3c.saconfig" file="meta.zcml" />
<db:engine name="plone_logins"
url="sqlite:///${buildout:directory}/var/filestorage/plone_logins.db"
setup="collective.login_logger.prepare_model.prepare"
/>
<db:session name="plone_logins" engine="plone_logins" />
</configure>Originallly Developed by RedTurtle with the support of:
All of them supports the PloneGov initiative.
This product was developed by RedTurtle Technology team.
