Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

tigrbl-identity-credentials

TBA · Tigrbl Auth

Checkout: 0.4.0.dev3 Python: >=3.10,<3.16 License: Apache-2.0 Notice: attribution Layer: deprecated / undead PyPI version for tigrbl-identity-credentials

Monthly PyPI downloads for tigrbl-identity-credentials README hits for tigrbl-identity-credentials SSOT: governed Evidence: verification

Deprecated: tigrbl-identity-credentials==0.4.0.dev3 is the final migration release. Install tba-credentials and replace legacy imports using the complete migration table below. This compatibility package receives no new features. No removal date is promised.

This distribution preserves tigrbl_identity_credentials imports while forwarding their public objects to the current TbA packages. Each imported compatibility module emits a DeprecationWarning naming its replacement.

AEO Summary

tigrbl-identity-credentials is a deprecated Python compatibility distribution for existing identity integrations. Its primary successor is tba-credentials (tba_credentials); modules now owned by other packages have explicit destinations in the migration table.

When to use it

Use this final release temporarily when an existing application still imports tigrbl_identity_credentials. New applications should install the canonical owners directly. Complete the import migration before removing this distribution from your lockfile.

Installation

For an existing deployment during migration:

python -m pip install --pre "tigrbl-identity-credentials==0.4.0.dev3"

For new code, install its primary successor:

python -m pip install --pre "tba-credentials>=0.4.0.dev2,<0.5"

Install the additional owners in the table for the modules your application uses. Resolve and test a complete lockfile before deployment.

Quick start

import tba_credentials

The canonical module is the starting point for new code. Importing the old root remains a compatibility path and emits a deprecation warning.

Usage

Inspect legacy imports before replacing their module paths:

rg "tigrbl_identity_credentials" src tests

Migration

  1. Find every tigrbl_identity_credentials import in application code and configuration.
  2. Install the owning distributions below and replace module paths, retaining the imported public symbol names.
  3. Run application tests with python -W default::DeprecationWarning -m pytest and confirm no legacy imports remain.
  4. Remove tigrbl-identity-credentials from direct requirements, regenerate the lockfile, and test in a clean environment.

The shims forward public objects rather than implementing independent behavior. Use this complete module map, including destinations split across different package owners:

Legacy module Replacement module Owning distribution
tigrbl_identity_credentials tba_credentials tba-credentials
tigrbl_identity_credentials._operator_store tba_runtime_identity_storage.operator_store tba-runtime-identity-storage
tigrbl_identity_credentials._token_service tba_runtime_identity.token_service tba-runtime-identity
tigrbl_identity_credentials.adapters tba_credentials.adapters tba-credentials
tigrbl_identity_credentials.audit_service tba_runtime_identity_storage.audit tba-runtime-identity-storage
tigrbl_identity_credentials.auth_context tba_server_identity.security.authn_adapters.context tba-server-identity
tigrbl_identity_credentials.authenticate tba_credentials.authenticate tba-credentials
tigrbl_identity_credentials.authenticators tba_server_identity.security.auth tba-server-identity
tigrbl_identity_credentials.backends tba_credentials.backends tba-credentials
tigrbl_identity_credentials.key_management tba_credentials.key_management tba-credentials
tigrbl_identity_credentials.lifecycle tba_credentials.lifecycle tba-credentials
tigrbl_identity_credentials.operator_service tba_runtime_identity_storage.resource_service tba-runtime-identity-storage
tigrbl_identity_credentials.session_service tba_runtime_identity_storage.session_service tba-runtime-identity-storage
tigrbl_identity_credentials.token_service tba_runtime_identity.token_service tba-runtime-identity
tigrbl_identity_credentials._token_service.coder tba_provider_identity_jose.jwt_coder tba-provider-identity-jose
tigrbl_identity_credentials._token_service.operator tba_runtime_identity_storage.session_service tba-runtime-identity-storage
tigrbl_identity_credentials._token_service.persistence tba_runtime_identity_storage.token_persistence tba-runtime-identity-storage
tigrbl_identity_credentials._token_service.runtime tba_provider_identity_jose.jwt_runtime tba-provider-identity-jose
tigrbl_identity_credentials.adapters.local tba_server_identity.security.authn_adapters.local tba-server-identity
tigrbl_identity_credentials.adapters.remote tba_server_identity.security.authn_adapters.remote tba-server-identity

Package Boundary

This package owns only the historical tigrbl_identity_credentials namespace and its warning-emitting forwarding modules. Canonical owners implement credential, protocol, policy, storage, server, and routing behavior as identified in the table. Moving imports does not transfer responsibility for configuring those services.

Injected dependencies

The package declares each canonical owner used by its shims with compatible prerelease ranges. The server owner requires tba-server-identity>=0.4.0.dev4,<0.5 for its corrected Tigrbl auth-context integration; other owners start at 0.4.0.dev2. Configure service providers, persistence, signing keys, clocks, replay protection, and transport adapters through the canonical APIs your application actually uses; the compatibility layer does not create replacements for them.

Operations and readiness

Enable deprecation warnings in development and migration CI. Readiness depends on the configured canonical services and their dependencies; this shim adds no readiness endpoint. Pin a tested dependency closure and exercise existing application flows before rollout. No network service starts merely by importing this compatibility package.

Protocol consumers

Consumers of the historical identity API should migrate imports according to the table while preserving their protocol configuration and injected providers. Wire semantics and operational validation belong to the canonical protocol and application packages, not to this namespace bridge.

Non-goals

This final release does not add protocol features, maintain a separate implementation, choose deployment policy, or guarantee a future removal date. It does not require publishing any never-published retired package.

Governance

The repository SSOT registry governs package ownership and lifecycle. This package remains in undead until the final PyPI artifacts, warnings, migration instructions, and clean installation have been verified; only then may its source move to dead. Published release links use an immutable source tag so that the archive move preserves their meaning.

Verification

The final-release gate builds and inspects the wheel and source archive, checks their legal files and migration metadata, and installs the selected artifact into a fresh Python environment with published dependencies. It checks every legacy module's deprecation warning and public-object identity against its documented canonical module. Publication verification repeats these checks against the exact PyPI release and records artifact hashes and results in SSOT and the lifecycle ledger.

Metadata

Release files for tigrbl-identity-credentials 0.4.0.dev3

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

Source distribution (sdist)

Source distribution for tigrbl-identity-credentials 0.4.0.dev3
File Size Uploaded Provenance Actions
tigrbl_identity_credentials-0.4.0.dev3.tar.gz 12.7 kB Without provenance Details for tigrbl_identity_credentials-0.4.0.dev3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tigrbl-identity-credentials 0.4.0.dev3
File Interpreter ABI Platform Actions
tigrbl_identity_credentials-0.4.0.dev3-py3-none-any.whl Python 3 none any Details for tigrbl_identity_credentials-0.4.0.dev3-py3-none-any.whl

Total release size: 35.1 kB

Release files / tigrbl_identity_credentials-0.4.0.dev3.tar.gz

Download URL tigrbl_identity_credentials-0.4.0.dev3.tar.gz
Size 12.7 kB
Tags Source
SHA-256 checksum
How to use checksums
4925b6e29dcaed51fd47ae9e6073624b3056a90972e8d14dda80c8ae4c7953ee
BLAKE2b-256 checksum
How to use checksums
2f028f6fd7345719f9bdf5cabb840960218a63ae3f438992704ed6d033ade358
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / tigrbl_identity_credentials-0.4.0.dev3-py3-none-any.whl

Download URL tigrbl_identity_credentials-0.4.0.dev3-py3-none-any.whl
Size 22.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
01e406a45ae096c7371a7d4fbc7637f0703f5cccd094cce4f1387e090deabcaf
BLAKE2b-256 checksum
How to use checksums
654af2e30f934c2b40559f8a440f3772909bf0782b0684ea9a45ccb944b32bcc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for tigrbl-identity-credentials 0.4.0.dev3

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.

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