This release is a pre-release and may not be stable for production use.
pipefy-auth
Shared OAuth + keychain helpers for Pipefy CLI and MCP server.
What lives here
storage— keychain-backedStoredSession(one entry per(issuer, client_id)tuple, under the OS keychain service namepipefy).flow— OAuth 2.0 Authorization Code with PKCE login flow.refresh— refresh-token grant + eager pre-use freshness check (ensure_fresh_session).discovery— OIDC.well-known/openid-configurationfetch + validation.revoke— IdP-side token invalidation (RFC 7009).identity—OidcClientdataclass + theDEFAULT_AUTH_CLIENT_IDconstant (the registered Keycloak public client_id).
Consumers
pipefy-cli and pipefy-mcp-server both depend on this package and read the same keychain entry, so a single pipefy auth login serves both binaries.
Metadata
Release files for pipefy-auth 0.5.3b1
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 |
|---|---|---|---|---|
| pipefy_auth-0.5.3b1-py3-none-any.whl | Python 3 | none | any | Details for pipefy_auth-0.5.3b1-py3-none-any.whl |
Release files / pipefy_auth-0.5.3b1-py3-none-any.whl
| Download URL | pipefy_auth-0.5.3b1-py3-none-any.whl |
|---|---|
| Size | 36.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
310ee3c42e3b805e1c109ee4e0446ceb560afe18e4ec72221ab582d9453de651
|
|
BLAKE2b-256 checksum How to use checksums |
31e7eaeafba659201627698add2be448fbeba3973d654b5f6b7b3679250394ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logSecurity for pipefy-auth 0.5.3b1
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.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for pipefy_auth-0.5.3b1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logA 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.