This release is a pre-release and may not be stable for production use.
Neon Users Service
This module manages access to a pluggable user database backend. By default, it operates as a standalone module using SQLite as the persistent data store.
Configuration
Configuration may be passed directly to the NeonUsersService constructor,
otherwise it will read from a config file using ovos-config. The configuration
file will be ~/.config/neon/diana.yaml by default. An example valid configuration
is included:
neon_users_service:
module: sqlite
sqlite:
db_path: ~/.local/share/neon/user-db.sqlite
module defines the backend to use and a config key matching that backend
will specify the kwargs passed to the initialization of that module.
MQ Integration
The mq_connector module provides an MQ entrypoint to services and is the
primary method of interaction with this service. Valid requests are detailed
below. Responses will always follow the form:
success: False
error: <string description>
success: True
user: <serialized User object>
Create
Create a new user by sending a request with the following parameters:
operation: create
username: <new_username>
password: <new_password>
user: <Optional serialized User object, else default will be created>
Read
Read an existing user. If password is not supplied, then the returned User
object will have the password_hash and tokens config redacted.
operation: read
username: <existing_username>
password: <existing_password>
Update
Update an existing user. If a password is supplied, it will replace the
user's current password. If no password is supplied and user.password_hash
is updated, the database entry will be updated with that new value.
operation: update
username: <existing_username>
password: <optional new password>
user: <updated User object>
Delete
Delete an existing user. This requires that the supplied user object matches
an entry in the database exactly for validation.
operation: delete
username: <username_to_delete>
user: <User object to delete>
Licensing
This project is free to use under the GNU Affero General Public License. Contact info@neon.ai for commercial licensing options.
Metadata
Release files for neon-users-service 0.0.1a6
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 |
|---|---|---|---|---|
| neon_users_service-0.0.1a6.tar.gz | 26.2 kB | Without provenance | Details for neon_users_service-0.0.1a6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neon_users_service-0.0.1a6-py3-none-any.whl | Python 3 | none | any | Details for neon_users_service-0.0.1a6-py3-none-any.whl |
Total release size: 56.5 kB
Release files / neon_users_service-0.0.1a6.tar.gz
| Download URL | neon_users_service-0.0.1a6.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd0b98217b8cf4425c6bf0be9b8890f7b2fc6e024e20be9926fda487327d1c10
|
|
BLAKE2b-256 checksum How to use checksums |
1692e8f9249965d67e2731cf97f31fe88e6fc6da833d5dad4ff53680d550921a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / neon_users_service-0.0.1a6-py3-none-any.whl
| Download URL | neon_users_service-0.0.1a6-py3-none-any.whl |
|---|---|
| Size | 30.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49ff7fadddfddaf5a4d14af8192d7492bedffbe83f452f892466914f15ca2b09
|
|
BLAKE2b-256 checksum How to use checksums |
16df0b40b843f0cc526d628306173eabca602131553471c2087a2a7a6e7c1f86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for neon-users-service 0.0.1a6
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.