This release is a pre-release and may not be stable for production use.
plone.oidc
Pure OpenID Connect implementation for Plone framework which is 100% comply with OpenID Connect Core 1.0 specifications. More over this product is Health Relationship Trust Profile for OAuth 2.0 complience with, so can be easily adaptable with HEART ecosystem.
Features
Dexterity Based Membrane user support.
Fullly RESTFull API complience
100% comply with HEART ecosystem.
Installation
Install plone.oidc by adding it to your buildout:
[buildout]
...
eggs =
plone.oidc
and then running bin/buildout
Contribute
Issue Tracker: https://github.com/nazrulworld/plone.oidc/issues
Source Code: https://github.com/nazrulworld/plone.oidc
Documentation: https://docs.plone.org/plone/oidc
Support
If you are having issues, please let us know. We have a mailing list located at: email@gmail.com
License
The project is licensed under the GPLv2.
Contributors
Md Nazrul Islam, email2nazrul@gmail.com
Changelog
1.0.0a2 (2018-07-20)
plone.oidc.membrane.behaviors.IOidConnectClaims behavior is available.
oidc_membrane_user_workflow workflow is available.
1.0.0a1 (2018-07-20)
Initial release. [nazrulworld]
1 maintainer
Metadata
1 maintainer
Release files for plone.oidc 1.0.0a2
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 | |
|---|---|---|---|---|
| plone.oidc-1.0.0a2.tar.gz | 21.6 kB | Without provenance | Details |
Release files / plone.oidc-1.0.0a2.tar.gz
| Download URL | plone.oidc-1.0.0a2.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
335c7dbbeeae7695950f3173b400d9d607c0149f4884756d0de63f8dcf86f9e6
|
|
BLAKE2b-256 checksum How to use checksums |
6537f6608f967e3adfd421b2694cb84c2d1264191a11df479e7550860ffa4a71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.oidc 1.0.0a2
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.
