https://github.com/redturtle/collective.login_monitor
Store and monitor login access to your Plone site
https://github.com/redturtle/collective.login_monitor
Last synced: 12 months ago
JSON representation
Store and monitor login access to your Plone site
- Host: GitHub
- URL: https://github.com/redturtle/collective.login_monitor
- Owner: RedTurtle
- Created: 2013-04-18T14:46:29.000Z (about 13 years ago)
- Default Branch: master
- Last Pushed: 2022-07-15T12:38:05.000Z (almost 4 years ago)
- Last Synced: 2025-03-31T03:51:40.486Z (over 1 year ago)
- Language: Python
- Homepage: http://plone.org/products/collective.login_monitor
- Size: 61.5 KB
- Stars: 4
- Watchers: 12
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.rst
Awesome Lists containing this project
README
Save any **login operation** done in your Plone site to an external database and provide a Plone interface
for query the database.
.. contents:: **Table of contents**
Introduction
============
This Plone add-on is based on `z3c.saconfig`__ and `SQLAlchemy`__, and can't provide any new feature to Plone
without a proper configuration.
__ http://pypi.python.org/pypi/z3c.saconfig
__ http://sqlalchemy.org/
Keep reading for installation and configuration guide.
How to use
==========
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: "*Monitor user logins*".
From this view you can query the database previously populated:
.. image:: http://blog.redturtle.it/pypi-images/collective.login_monitor/collective.login_monitor-0.2-01.png
:alt: Control panel for login monitor
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.
Multiple sites
--------------
If your buildout hosts multiple Plone sites, all of them will store data in the database keeping same username
on different sites separated.
Installation and configuration
==============================
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**).
__ http://www.sqlite.org/
Add ``collective.login_monitor`` to your buildout, then provide a SQLAlchemy connection string::
[buildout]
...
[instance]
...
eggs=
...
collective.login_monitor
zcml-additional =
...
Credits
=======
Developed with the support of:
* `Azienda USL Ferrara`__
.. image:: http://www.ausl.fe.it/logo_ausl.gif
:alt: Azienda USL's logo
* `S. Anna Hospital, Ferrara`__
.. image:: http://www.ospfe.it/ospfe-logo.jpg
:alt: S. Anna Hospital - logo
All of them supports the `PloneGov initiative`__.
__ http://www.ausl.fe.it/
__ http://www.ospfe.it/
__ http://www.plonegov.it/
Authors
=======
This product was developed by RedTurtle Technology team.
.. image:: http://www.redturtle.it/redturtle_banner.png
:alt: RedTurtle Technology Site
:target: http://www.redturtle.it/