eoepca_scim
Auxiliary Python3 library that allows a client to dynamically register with Gluu and access SCIM endpoints to get/add/edit/remove user attributes
Explore the docs
.
Report Bug
·
Request Feature
Table of Contents
- Setup this template!
- Table of Contents
- About The Project
- Getting Started
- Documentation & Usage
- Roadmap
- Contributing
- License
- Contact
- Acknowledgements
About The Project
This is an auxiliary Python3 library to allow a client to dynamically register with Gluu. At the same time, it allows to get all user attributes, and also add/edit/remove specific attributes, by using SCIM endpointsWith both OAuth and UMA tokens.
Built With
Prerequisites
Installation
Download the library using pip
pip install eoepca-scim
Enable Test Mode in Gluu by following these procedures: Protection using Test Mode Disable Test Mode and Enable UMA by following these procedures: Protection using UMA
Documentation & Usage
The component documentation can be found at https://eoepca.github.io/um-common-scim-client/.
For example usages, check main.py
Roadmap
See the open issues for a list of proposed features (and known issues).
Contributing
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
License
Distributed under the Apache-2.0 License. See LICENSE for more information.
Contact
Project Link: https://github.com/EOEPCA/um-common-scim-client
Acknowledgements
- README.md is based on this template by Othneil Drew.
Metadata
Release files for eoepca-scim 2.8.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 |
|---|---|---|---|---|
| eoepca-scim-2.8.1.tar.gz | 13.3 kB | Without provenance | Details for eoepca-scim-2.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eoepca_scim-2.8.1-py3-none-any.whl | Python 3 | none | any | Details for eoepca_scim-2.8.1-py3-none-any.whl |
Total release size: 25.5 kB
Release files / eoepca-scim-2.8.1.tar.gz
| Download URL | eoepca-scim-2.8.1.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35ad8ba8b4d8ee3c076a6d7c618681e8b09287633958ebad8d7465110d30608f
|
|
BLAKE2b-256 checksum How to use checksums |
1dd3d690465028ca6fe23b7afe8dc8f9f2ab7da1318ab0cee57b34e02dfec1b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.1
|
Release files / eoepca_scim-2.8.1-py3-none-any.whl
| Download URL | eoepca_scim-2.8.1-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a728367d211fc1b0f9958bf1bc96b63e23965840f71f52a5d1b7a004bce5f6a
|
|
BLAKE2b-256 checksum How to use checksums |
40522699e40924ef3a3dedb391cf790ea9b4e03e0747b53c032d8ae0eda65d27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.1
|
Security for eoepca-scim 2.8.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.