openstack-s11-auth
install
pip install openstack-s11auth
OR
brew install openstackclient
python3 -m pip --python /opt/homebrew/Cellar/openstackclient/$(brew info openstackclient --json | jq -r '.[].linked_keg')/libexec/bin/python install openstack-s11auth
OR
git clone $REPO && cd $REPO
pip install -e .
usage
export OS_AUTH_URL="https://$KEYSTONE:5000/v3/"
export OS_AUTH_TYPE="v3s11"
openstack project list
Use --os-redirect-port 8181 to change the port of the local redirect server in case it's occupied already.
Helper: Differently scoped tokens on password auth
# project-scoped
openstack --os-auth-type "password" --os-username "admin" --os-project-name "myproject" --os-project-domain-id "default" --os-user-domain-id "default" --os-auth-url "http://localhost:8001/v3" project set --description "foobar" myproject
# domain-scoped
openstack --os-auth-type "password" --os-username "admin" --os-domain-id "default" --os-user-domain-id "default" --os-auth-url "http://localhost:8001/v3" project set --description "foobar" myproject
Metadata
Release files for openstack-s11auth 1.0.3
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 |
|---|---|---|---|---|
| openstack_s11auth-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for openstack_s11auth-1.0.3-py3-none-any.whl |
Release files / openstack_s11auth-1.0.3-py3-none-any.whl
| Download URL | openstack_s11auth-1.0.3-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7eee0f2aac7ad80c4f89858072d530b5709e288a7c21035e4801aa2d2a2d9dcd
|
|
BLAKE2b-256 checksum How to use checksums |
2ee8aa8edab50b83fe113d18175231a1dc62ee7b7a795305adfb56f1ab945a04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Security for openstack-s11auth 1.0.3
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.