From de3698f53588cff7a803137f4fc5b36f54574487 Mon Sep 17 00:00:00 2001 From: Willem de Groot Date: Fri, 10 Mar 2023 14:13:56 +0100 Subject: [PATCH] Clarify possible credential storage locations (#11358) --- doc/articles/authentication-for-private-packages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/articles/authentication-for-private-packages.md b/doc/articles/authentication-for-private-packages.md index f84a9afa1..1def99f18 100644 --- a/doc/articles/authentication-for-private-packages.md +++ b/doc/articles/authentication-for-private-packages.md @@ -28,8 +28,8 @@ for credentials and save them (or a token if Composer is able to retrieve one). Sometimes automatic authentication is not possible, or you may want to predefine authentication credentials. -Credentials can be stored on 3 different places; in an `auth.json` for the project, a global -`auth.json` or in the `composer.json` itself. +Credentials can be stored on 4 different places; in an `auth.json` for the project, a global +`auth.json`, in the `composer.json` itself or in the `COMPOSER_AUTH` environment variable. ## Authentication in auth.json per project