Aos user keys management tool
This tool is part of the AosEdge SDK.
Overview
This tool will help you manage user certificates for Aos Cloud.
Using this tool you'll be able to:
- Issue new user certificate in pkcs12 format.
- Show info about user certificate.
- Convert PKCS12 certificate to PEM key and certificate files.
Prerequisites
- Python 3.7+
Installation
python -m pip install aos-keys
Usage
Issue new user certificate:
aos-keys new-user -d {aoscloud.io} -t {token} {--oem|--sp|--fleet}
Where:
- -d - Aos CLoud domain to register user
- -t - User Token
- -oem or -sp - Certificate for OEM or SP User
Example:
aos-keys new-user -d aoscloud.io -t 1111 --oem
Show info about certificate and related user:
aos-keys info -c {path-to-cert} {--oem|--sp|--fleet}
Where:
- -c - Path to user certificate
- -sp - Show info of default Service Provider user
- -oem - Show info of default OEM user
- -fleet - Show info of default Fleet Owner user
Example: Show info about default SP user certificate
aos-keys info --sp
Show info about default OEM user certificate
aos-keys info --oem
Metadata
Release files for aos-keys 1.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aos_keys-1.10.1-py3-none-any.whl | Python 3 | none | any | Details for aos_keys-1.10.1-py3-none-any.whl |
Release files / aos_keys-1.10.1-py3-none-any.whl
| Download URL | aos_keys-1.10.1-py3-none-any.whl |
|---|---|
| Size | 23.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05a68794213593f680cd26057f538def7d35f70ce3a0743dd51467cfcf0cd49c
|
|
BLAKE2b-256 checksum How to use checksums |
ee5a970c0de2e82c29f86d43191718e323e726c0c7aa210822bc03b9d7f524ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for aos-keys 1.10.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.