A user account management plugin for Trac.
== Installation ==
1. Run: python setup.py bdist_egg
2. If necessary, create a folder called "plugins" in your Trac environment.
3. Copy the .egg file from the "dist" folder created by step 1
into the "plugins" directory of your Trac environment.
== Configuration ==
Add one of the following sections to trac.ini to get started. See even
more configuration examples for supported backends at
http://trac-hacks.org/wiki/AccountManagerPlugin/AuthStores
or in the configuraition cookbook page at
http://trac-hacks.org/wiki/CookBook/AccountManagerPluginConfiguration
=== Htpasswd ===
{{{
[account-manager]
; use an Apache htpasswd file
htpasswd_hash_type = md5
htpasswd_file = /path/to/trac.htpasswd
password_store = HtPasswdStore
}}}
=== Htdigest ===
{{{
[account-manager]
; use an Apache htdigest file
htdigest_file = /path/to/trac.htdigest
htdigest_realm = TracDigestRealm
password_store = HtDigestStore
}}}
=== HttpAuth ===
{{{
[account-manager]
; use a page that is secured with HTTP Auth
authentication_url = http://hostname/path
password_store = HttpAuthStore
}}}
Metadata
Release files for TEST-TracAccountManager 0.5
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 |
|---|---|---|---|---|
| test-tracaccountmanager.tar.gz | 674.3 kB | Without provenance | Details for test-tracaccountmanager.tar.gz |
Release files / test-tracaccountmanager.tar.gz
| Download URL | test-tracaccountmanager.tar.gz |
|---|---|
| Size | 674.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5daad331446c9d2dd5fed3219d0974736bbcc90787f3c6964df81d62d44c23f3
|
|
BLAKE2b-256 checksum How to use checksums |
3c2e878cdb5c7f25c3e85c649a18b65f45828688a7814e1bfcbeaa903dbe3f8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TEST-TracAccountManager 0.5
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.