From 9b5e804c6a21a5bd8d6b95e1499d0dc3fc2592ae Mon Sep 17 00:00:00 2001
From: Adrian Mouat <adrian@chainguard.dev>
Date: Thu, 15 Aug 2024 08:30:57 +0100
Subject: [PATCH] Remove OOD info on enterprise. (#1737)

Deleted section on enterprise usage.

This section did explain how to use the API with a long-lived token,
which is still potentially useful, but it would need updated and
checked. The remaining instructions are preferable as they don't involve
long-lived tokens. Given the instructions have been broken for a
long-time and no-one complained, I don't think anyone will miss it.

Signed-off-by: Adrian Mouat <adrian@chainguard.dev>
---
 .../using-the-tag-history-api.md              | 95 +------------------
 1 file changed, 1 insertion(+), 94 deletions(-)

diff --git a/content/chainguard/chainguard-images/working-with-images/using-the-tag-history-api.md b/content/chainguard/chainguard-images/working-with-images/using-the-tag-history-api.md
index 4eb0e458b7..3f2464a897 100644
--- a/content/chainguard/chainguard-images/working-with-images/using-the-tag-history-api.md
+++ b/content/chainguard/chainguard-images/working-with-images/using-the-tag-history-api.md
@@ -7,7 +7,7 @@ aliases:
 type: "article"
 description: "Learn how to use the Chainguard Images Tag History API to fetch the tag history of image variants."
 date: 2023-05-26T08:49:31+00:00
-lastmod: 2024-03-21T15:22:20+01:00
+lastmod: 2024-08-02T15:22:20+01:00
 draft: false
 tags: ["Chainguard Images", "Product"]
 images: []
@@ -119,96 +119,3 @@ FROM cgr.dev/chainguard/python@sha256:81c334de6dd4583897f9e8d0691cbb75ad41613474
 
 And your image will then be locked into that specific build of the `python:latest` image variant.
 
-## Accessing the History API for Enterprise Images
-
-If you are a customer who would like to access the history API for Enterprise images, you must create credentials to access the API with curl and Bash.
-
-### Create Credentials
-
-You'll need to use credentials to access the Registry. First, authenticate with `chainctl`.
-
-```sh
-chainctl auth login
-```
-
-Next, retrieve your Organization's UIDP and store it in a variable.
-
-```sh
-chainctl iam organizations ls -o table
-```
-```
-export ORG_ID="cc...52"
-```
-
-At this point, you can create a token for 30 days. Note that 30 days is the default, the max you can initialize a token for is 1 year.
-
-```sh
-chainctl auth configure-docker --pull-token --parent $ORG_ID --ttl 720h
-```
-
-If you would like to use this pull token in another environment, run this command with Docker.
-
-```sh
-docker login "cgr.dev" --username "cc..96" --password "eyJ...X34"
-```
-
-Be sure to keep a copy of the username and password created.
-
-### Optional: Storing Credentials
-
-You can use the username and password you just created if required. However, Docker's default functionality is to encode these credentials in base64 and then store them within `~/.docker/config.json`.
-
-To set that up, following the previous example, replace the username and password value, keeping the colon (`:`) to separate the values.
-
-```sh
-echo -n "username:password" | base64
-Y2M...Wc=
-```
-
-Add the base64 encoded value to `~/.docker/config.json` with the following format:
-
-```sh
-{
-  "auths": {
-    "cgr.dev": {
-      "auth": "Y2M...Wc="
-    }
-  }
-}
-```
-
-You can review more about Docker Configs from the [official Docker docs](https://docs.docker.com/engine/swarm/configs/).
-
-### Access the History API with curl and Bash
-
-Now that we have the credentials, we can use curl and Bash to access the endpoints (the following example uses jq as well). Here, you will replace `private-registry.com/apko` with your relevant Registry and Image information.
-
-```sh
-IMAGE=private-registry.com/apko
-USERNAME="cc..96"
-PASSWORD="eyJ...X34"
-export TOKEN=$(echo -n "${USERNAME}:${PASSWORD}" | base64 | tr -d '\n\r')
-curl -s -H "Authorization: Bearer \
-  $(curl -s -H "Authorization: Basic $TOKEN" \
-  "https://cgr.dev/token?scope=repository:${IMAGE}:pull" | jq -r .token)" \
-  "https://cgr.dev/v2/${IMAGE}/_chainguard/history/latest" | jq .
-```
-
-If you have set a `~/.docker/config.json` file within the optional step, you can run the following.
-
-```sh
-IMAGE=private-registry.com/apko
-curl -s -H "Authorization: Bearer \
-  $(curl -s -H "Authorization: Basic \
-  $(jq -r ".auths[\"cgr.dev\"].auth" < ~/.docker/config.json)" \
-  "https://cgr.dev/token?scope=repository:${IMAGE}:pull" | jq -r .token)" \
-  "https://cgr.dev/v2/${IMAGE}/_chainguard/history/latest" | jq .
-```
-
-Again, you would replace `private-registry.com/apko` with your relevant Registry and Image information.
-
-## Images and Tags
-
-Public Chainguard Images are available at no cost to users, and do not require authentication. This gives access to the `latest` and `latest-dev` tags of our public images. Other versions and tags are available through subscription to our paid enterprise images, featuring enterprise-grade patching SLAs and customer support.
-
-To learn more about public and enterprise images, check our [Images FAQ page](/chainguard/chainguard-images/faq/#what-options-do-i-have-to-use-chainguard-images) about catalog tiers.