Introduction
This package provides logging of user names in Zope’s access log files when using cookie-based authentication as provided by PluggableAuthService and plone.session.
Installation
The easiest way to use this package is when working with installations based on zc.buildout. Here you can simply add the package to your “eggs” and “zcml” options, run buildout and restart your Zope/Plone instance.
Alternatively you can use the following configuration file to extend your existing buildout:
[buildout] extends = buildout.cfg [instance] eggs += collective.usernamelogger zcml += collective.usernamelogger
After that you should see user names being logged in your access log file, typically at <site-root>/var/log/instance-Z2.log.
Changelog
1.4 (2016-02-25)
Make session cookie name configurable via environment variable: Using the env variable USERNAMELOGGER_AC_COOKIE_NAME, the session cookie name can be set to a different value than the default of ‘__ac’. [lgraf]
1.3 (2015-06-12)
Don’t crash if we get a CookieError. [vincentfretin]
Properly deal with doubly quoted __ac cookies (e.g. from PAS.CookieAuthHelper). [lgraf]
skip binascii.Error [kroman0]
Added getting real client ip [kroman0]
1.2 (2011-08-16)
Added support for Plone 4.x session cookies. [buchi]
Handle auth cookies that aren’t hex encoded (used in PluggableAuthService < 1.5). [buchi]
Add z3c.autoinclude entry point for automatic ZCML loading in Plone 3.3+. [witsch]
1.1 (2010-01-07)
Unquote the cookie value before attempting to decode it. [vincentfretin]
1.0 (2009-08-08)
Re-release unchanged 1.0a2 as final. [witsch]
1.0a2 (2009-07-24)
Split session cookie from the right as the token can also contain spaces. [witsch]
Handle session cookies first as they can contain a colon, thereby breaking the hexadecimal decode. [witsch]
1.0a1 (2009-07-23)
Initial release [witsch]
Metadata
Release files for collective.usernamelogger 1.4
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 |
|---|---|---|---|---|
| collective.usernamelogger-1.4.tar.gz | 6.3 kB | Without provenance | Details for collective.usernamelogger-1.4.tar.gz |
Release files / collective.usernamelogger-1.4.tar.gz
| Download URL | collective.usernamelogger-1.4.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e599eea2eb762a4d2ced7fff05327a8bfc1328dd9d9f2ed9f6ef6ad6af5995a
|
|
BLAKE2b-256 checksum How to use checksums |
4b64f21bdbc7a6cb4c1eab38cfaacd4e3cd09a4b8c65eb74478d909b62aedb20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.usernamelogger 1.4
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.