Skip to main content

Authorization for the gRPC client

PyPI Python License

English | Русский

Issue and refresh IAM access tokens for the gRPC client.

Installation

Requires Python 3.13 or later.

pip install cloudru-qa-grpc-client-auth

Import the library as the grpc_client_auth module.

Skills for AI agents

This library does not have its own skill yet. If your project has other libraries from this collection with skills for AI agents, select and install them from the project root (requires uv):

uvx library-skills

For Claude Code, add --claude.

Usage

Synchronous client

from grpc_client import options
from grpc_client_auth import IAM_GrpcAuth, IAM_HttpClient

iam_client = IAM_HttpClient("https://iam.example.com")
client = MyGrpcClient.from_addr(
    "service.example.com:443",
    options.with_auth(IAM_GrpcAuth("my_key_id", "my_key_secret", iam_client)),
)

response = client.send_example_request(...)

client.close()
iam_client.close()

IAM_GrpcAuth implements grpc_client.ClientAuth, so connect it with the standard options.with_auth option.

Asynchronous client

from grpc_client import options
from grpc_client_auth import IAM_AsyncHttpClient, IAM_GrpcAsyncAuth

iam_client = IAM_AsyncHttpClient("https://iam.example.com")
client = MyAsyncGrpcClient.from_addr(
    "service.example.com:443",
    options.with_auth(IAM_GrpcAsyncAuth("my_key_id", "my_key_secret", iam_client)),
)

response = await client.send_example_request(...)

await client.close()
await iam_client.aclose()

What the library does

  • obtains an IAM token and stores it until expiry;
  • issues a new token when it expires or the service returns UNAUTHENTICATED;
  • avoids another IAM call if a concurrent request has already refreshed the token.

The gRPC client itself adds the authorization header and retries the request; see "Authorization" in its README.

Create one authorization object per set of credentials and reuse it across clients: IAM call deduplication works within one object.

Two IAM APIs are available for authorization:

Client Route
IAM_HttpClient, IAM_AsyncHttpClient POST /api/v1/auth/token
IAM_OpenID_HttpClient, IAM_OpenID_AsyncHttpClient POST /auth/system/openid/token

Token store

By default, tokens are stored in process memory. To share them across processes, implement AuthStore (or AsyncAuthStore for asynchronous usage):

from datetime import datetime

from grpc_client_auth import AuthStore, Token


class RedisAuthStore(AuthStore):
    """Redis token store."""

    def __init__(self, redis_client):
        self._redis = redis_client

    def get(self, key: str) -> Token | None:
        raw = self._redis.hgetall(f"token:{key}")
        if not raw:
            return None
        return Token(raw["access_token"], datetime.fromisoformat(raw["expires_at"]))

    def set(self, key: str, token: Token) -> None:
        self._redis.hset(
            f"token:{key}",
            mapping={
                "access_token": token.access_token,
                "expires_at": token.expires_at.isoformat(),
            },
        )


auth = IAM_GrpcAuth("my_key_id", "my_key_secret", iam_client, store=RedisAuthStore(...))

Token stores the token value and the time from which it is considered unusable. Its lifetime comes from the IAM response's expires_in field, minus a small margin to prevent expiry in transit.

Masking secrets in logs

If the IAM HTTP client logs requests, add IAM-specific masking keys; otherwise the OpenID request's secret key and the response JWT appear in full in the log:

from http_client import options as http_options
from grpc_client_auth import IAM_SANITIZE_KEYS, IAM_HttpClient

iam_client = IAM_HttpClient(
    "https://iam.example.com",
    http_options.with_logger(logger, sanitize_keys=IAM_SANITIZE_KEYS),
)

Components

IAM HTTP clients, the token store, and the token model come from cloudru-qa-http-client-auth and are re-exported here to keep imports simple.

That library also provides IAM_Auth and IAM_AsyncAuth, which authorize the HTTP client (httpx.Auth) and follow a different contract. For the gRPC client, use this library's IAM_GrpcAuth and IAM_GrpcAsyncAuth.

Development

The library is developed in the qa-libraries monorepo alongside the other cloudru-qa-* libraries. You need uv, GNU Make, and checkmake. Run commands from the repository root:

make sync                          # install dependencies for all libraries from uv.lock
make test-grpc-client-auth         # tests for this library
make typecheck-grpc-client-auth    # mypy for this library
make check                         # formatting, ruff, mypy, and tests for the entire workspace

Tests require Docker running: the grpcbin service container is started automatically, and the test API is generated from proto/ before execution. IAM requests in tests are intercepted with pytest-httpx.

Tests run on Python 3.13 and 3.14. Create a separate environment for another version: make sync test-grpc-client-auth PYTHON_VERSION=3.14.

Publish a release with the git tag grpc-client-auth/v<version>. The tag version must match the version in packages/grpc-client-auth/pyproject.toml.

Metadata

Release files for cloudru-qa-grpc-client-auth 1.0.0

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

Source distribution (sdist)

Source distribution for cloudru-qa-grpc-client-auth 1.0.0
File Size Uploaded Provenance Actions
cloudru_qa_grpc_client_auth-1.0.0.tar.gz 18.2 kB With provenance Details for cloudru_qa_grpc_client_auth-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cloudru-qa-grpc-client-auth 1.0.0
File Interpreter ABI Platform Actions
cloudru_qa_grpc_client_auth-1.0.0-py3-none-any.whl Python 3 none any Details for cloudru_qa_grpc_client_auth-1.0.0-py3-none-any.whl

Total release size: 29.1 kB

Release files / cloudru_qa_grpc_client_auth-1.0.0.tar.gz

Download URL cloudru_qa_grpc_client_auth-1.0.0.tar.gz
Size 18.2 kB
Tags Source
SHA-256 checksum
How to use checksums
737b42c5b68f61f39c219f3016537755452fe32d5b3634163ca396cfe7914966
BLAKE2b-256 checksum
How to use checksums
291c33efc3279a88bc1a00d4f4e6cf3416a3313bf187f68945427ddee33f1201
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Release files / cloudru_qa_grpc_client_auth-1.0.0-py3-none-any.whl

Download URL cloudru_qa_grpc_client_auth-1.0.0-py3-none-any.whl
Size 10.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f692bb24b0d0562e45e1f1fb27a4eb3a0d7b8cdaf9f8fee82519cf44caa89074
BLAKE2b-256 checksum
How to use checksums
f9f6098cb55b0f123c505888d08c735a19f0f580c1218fc9711e6f1d13ee1194
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 14, 2026.

Transparency log

Security for cloudru-qa-grpc-client-auth 1.0.0

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cloudru_qa_grpc_client_auth-1.0.0.tar.gz

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 Nov 14, 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.

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files Full provenance

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