IBM Cloud Container Registry Deprecates Registry Tokens for Authentication

1 min read

Back in June 2019, we announced the discontinuation of registry tokens as an authentication mechanism as we moved to a more secure IAM API key approach.

This announcement also aligned to the domain name changes. We made a second announcement in February 2020 about IBM Cloud Container Registry not accepting registry tokens for authentication. 

Effective August 19, 2021, any registry pulls that are using registry tokens will stop working, including pulls from IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud. Any registry pushes using registry tokens from CI pipelines will also stop working.

How do I avoid disruption?

You should automate access to your IBM Cloud Container Registry namespaces so you can push and pull images using IBM Cloud Identity and Access Management (IAM). Learn more:

  1. Automating access using IAM
  2. IBM Cloud Kubernetes Service and IBM Cloud Container Registry
  3. Red Hat OpenShift on IBM Cloud and IBM Cloud Container Registry

Join the conversation

If you have questions or concerns, engage our team via Slack. You can register here and join the discussion in the #general channel on

Be the first to hear about news, product updates, and innovation from IBM Cloud