Metadata-Version: 2.4
Name: artifact-keeper-client
Version: 1.2.4
Summary: Artifact Keeper API
Home-page: https://github.com/artifact-keeper/artifact-keeper-api
Author: Artifact Keeper
Author-email: team@openapitools.org
License: MIT
Keywords: OpenAPI,OpenAPI-Generator,Artifact Keeper API
Description-Content-Type: text/markdown
Requires-Dist: urllib3<3.0.0,>=1.25.3
Requires-Dist: python-dateutil>=2.8.2
Requires-Dist: pydantic>=2
Requires-Dist: typing-extensions>=4.7.1
Dynamic: author
Dynamic: author-email
Dynamic: description
Dynamic: description-content-type
Dynamic: home-page
Dynamic: keywords
Dynamic: license
Dynamic: requires-dist
Dynamic: summary

    Enterprise artifact registry supporting 45+ package formats.  ## Authentication  The JSON management API under &#x60;/api/v1/*&#x60; accepts **API tokens only as &#x60;Authorization: Bearer &lt;token&gt;&#x60;**. This is the canonical scheme for programmatic access; JWTs issued by the login flow also use &#x60;Bearer&#x60;. HTTP Basic credentials on &#x60;/api/v1/*&#x60; are validated *only* as a real &#x60;username:password&#x60; login — the password half is **not** retried as an API token. A request to &#x60;/api/v1/*&#x60; that sends an API token in the password field of Basic auth therefore returns &#x60;401 AUTH_ERROR&#x60;; switch to &#x60;Authorization: Bearer &lt;token&gt;&#x60;.  Format (package-manager) endpoints such as &#x60;/v2/*&#x60; (OCI), &#x60;/incus/*&#x60;, &#x60;/debian/*&#x60;, and the language registries are intentionally more permissive for client compatibility: in addition to Bearer, they accept HTTP **Basic** auth with the API token supplied in the *password* field (any username), matching the &#x60;pip&#x60; netrc / Artifactory-style &#x60;token:&lt;api_token&gt;&#x60; convention used by package managers that cannot send a Bearer header. This Basic-with-token fallback applies to format endpoints only, never to &#x60;/api/v1/*&#x60;.
    
