Skip to main content
Pre-release

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-backed StoredSession (one entry per (issuer, client_id) tuple, under the OS keychain service name pipefy).
  • 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-configuration fetch + validation.
  • revoke — IdP-side token invalidation (RFC 7009).
  • identity — OidcClient dataclass + the DEFAULT_AUTH_CLIENT_ID constant (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.4b1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for pipefy-auth 0.5.4b1
File Interpreter ABI Platform Actions
pipefy_auth-0.5.4b1-py3-none-any.whl Python 3 none any Details for pipefy_auth-0.5.4b1-py3-none-any.whl

Release files / pipefy_auth-0.5.4b1-py3-none-any.whl

Download URL pipefy_auth-0.5.4b1-py3-none-any.whl
Size 36.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
16cb2b19f1a6511e49f1a808878a104001e3976f6925e23ca55e5b3b758719f8
BLAKE2b-256 checksum
How to use checksums
16e94d47a7dc740040a59c07264fd5d607795d3a2b58d3d298c00153c222dec5
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 9, 2026.

Transparency log

Security for pipefy-auth 0.5.4b1

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.4b1-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 9, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page