| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-08-02 |
IBM Cloud Container Registry notices, notices, registry tokens, authentication |
Registry |
{{site.data.keyword.attribute-definition-list}}
{{site.data.keyword.registryshort}} discontinues registry tokens for authentication on 19 August 2021
{: #registry_notices_token_auth}
From 19 August 2021, any {{site.data.keyword.registrylong}} pulls that use registry tokens stop working, including pulls from {{site.data.keyword.containerlong_notm}}{: external} and {{site.data.keyword.openshiftlong}}{: external}. Any {{site.data.keyword.registryshort}} pushes that use registry tokens from CI pipelines also stop working. {: shortdesc}
The discontinuation of registry tokens as an authentication mechanism for {{site.data.keyword.registrylong_notm}} was announced in June 2019 as {{site.data.keyword.registryshort}} moved to a more secure IAM API key approach. This announcement is also aligned to the icr.io domain name changes. A further announcement was issued in February 2020 about {{site.data.keyword.registryshort}} not accepting registry tokens for authentication.
{: #registry_notices_token_auth_action}
You must automate access to your {{site.data.keyword.registryshort}} namespaces so that you can push and pull images by using {{site.data.keyword.iamlong}} (IAM) by 19 August 2021.
{: #registry_notices_token_auth_learn}
For more information about how to automate access to your {{site.data.keyword.registryshort}} namespaces see the following topics.
- Automating access by using IAM
- {{site.data.keyword.containerlong_notm}} and {{site.data.keyword.registrylong_notm}}
- {{site.data.keyword.openshiftlong_notm}} and {{site.data.keyword.registrylong_notm}}
{: #registry_notices_token_auth_announce}
The original announcement that this notification mirrors is {{site.data.keyword.registrylong_notm}} Deprecates Registry Tokens for Authentication{: external} and it was published on 28 May 2021.