Chainguard Container for hydra-fips

Ory Hydra is a hardened, OpenID Certified OAuth 2.0 Server and OpenID Connect Provider optimized for low-latency, high throughput, and low resource consumption.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/hydra-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard Hydra Image is comparable to the official Hydra Image from Docker Hub. However, the Chainguard image contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a package manager.

Getting Started

Chainguard image can be used as a drop in replacement in the Helm charts offered by Hydra.

The following is an example values.yaml file. Be sure to change the image repository and tag placeholders:

hydra:
  dev: true
  automigration:
    enabled: true
  config:
    dsn: "postgres://hydrauser:securepassword@postgres-postgresql.default.svc.cluster.local:5432/hydradb?sslmode=disable"
    urls:
      self:
        public: "https://hydra.example.com/"
        admin: "https://admin.hydra.example.com/"
      login: "https://auth.example.com/login"
      consent: "https://auth.example.com/consent"
    secrets:
      system:
        - "MY_SUPER_SECURE_SECRET_KEY"
image:
  repository: cgr.dev/ORGANIZATION/hydra-fips
  tag: latest

Run helm install:

helm repo add ory https://k8s.ory.sh/helm/charts
helm install hydra ory/hydra --values values.yaml --wait

Following that, port forward the services:

kubectl port-forward -n default svc/hydra-admin 4445:4445 &
kubectl port-forward -n default svc/hydra-public 4444:4444 &

Next create a client:

CLIENT_INFO=$(kubectl exec -it $(kubectl get pods -n default -l app.kubernetes.io/name=hydra -o jsonpath='{.items[0].metadata.name}') -n default -- \
hydra create oauth2-client --endpoint http://127.0.0.1:4445 \
--name "my-client" \
--secret "my-secret" \
--grant-type client_credentials \
--response-type token \
--scope read,write \
--token-endpoint-auth-method client_secret_post --format json)

Extract Client ID from the JSON output:

CLIENT_ID=$(echo $CLIENT_INFO | jq -r '.client_id')

Check the clients with kubectl:

kubectl exec -it $(kubectl get pods -n default -l app.kubernetes.io/name=hydra -o jsonpath='{.items[0].metadata.name}') -n default -- \
hydra list oauth2-clients --endpoint http://127.0.0.1:4445

Finally, use the dynamically retrieved Client ID in the curl request to verify the token works:

curl -X POST \
-d "client_id=$CLIENT_ID" \
-d "client_secret=my-secret" \
-d "grant_type=client_credentials" \
-d "scope=read" \
http://127.0.0.1:4444/oauth2/token

Documentation and Resources

For more information on working with Hydra, refer to the official quickstart documentation.

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.