Flat file authentication plugin for StackStorm Community edition
Flat file backend supports reading credentials from an Apache HTTPd htpasswd formatted file. To manage this file you can use htpasswd utility which comes with a standard Apache httpd distribution or by installing apache2-utils package on Ubuntu / Debian.
Configuration Options
| option | required | default | description |
|---|---|---|---|
| file_path | yes | Path to the file containing credentials |
Configuration Example
Please refer to the authentication section in the StackStorm documentation for basic setup concept. The following is an example of the auth section in the StackStorm configuration file for the flat-file backend.
[auth]
mode = standalone
backend = flat_file
backend_kwargs = {"file_path": "/path/to/.htpasswd"}
enable = True
use_ssl = True
cert = /path/to/ssl/cert/file
key = /path/to/ssl/key/file
logging = /path/to/st2auth.logging.conf
api_url = https://myhost.example.com:9101
debug = False
The following is an example htpasswd command to generate a password file with a user entry. You should be using no other hashing algorithm than bcrypt as it is consider the only secure hashing algorithm amoung all the algorithms supported by htpasswd.
htpasswd -cB /path/to/.htpasswd stark
Copyright, License, and Contributors Agreement
Copyright 2025 StackStorm, Inc. Copyright 2015 StackStorm, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this work except in compliance with the License. You may obtain a copy of the License in the LICENSE file, or at: http://www.apache.org/licenses/LICENSE-2.0
By contributing you agree that these contributions are your own (or approved by your employer) and you grant a full, complete, irrevocable copyright license to all users and developers of the project, present and future, pursuant to the license of the project.
Metadata
Release files for st2-auth-backend-flat-file 0.4.1
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 |
|---|---|---|---|---|
| st2-auth-backend-flat-file-0.4.1.tar.gz | 13.1 kB | Without provenance | Details for st2-auth-backend-flat-file-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| st2_auth_backend_flat_file-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for st2_auth_backend_flat_file-0.4.1-py3-none-any.whl |
Total release size: 27.1 kB
Release files / st2-auth-backend-flat-file-0.4.1.tar.gz
| Download URL | st2-auth-backend-flat-file-0.4.1.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6eb2e6e4f957fc31e85698232fbc7cda0b84580a93fd87f8797eae95c5dd4659
|
|
BLAKE2b-256 checksum How to use checksums |
8e5e19b41cc213bedef9107a8ad0d8c21107bc7c26dd54697fd8611051914c41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / st2_auth_backend_flat_file-0.4.1-py3-none-any.whl
| Download URL | st2_auth_backend_flat_file-0.4.1-py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca78524b296fd1ece20a4515d2eb745d31a06e7e7845beb1bf1dbf0baa35687b
|
|
BLAKE2b-256 checksum How to use checksums |
28c7ce6a10b839e08482d686290201f05b227e724c2aeafadc3bf579dbe7c346
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for st2-auth-backend-flat-file 0.4.1
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.