From 2dbc9447b5a9cc7ece8a413edacc3665f0a7005c Mon Sep 17 00:00:00 2001 From: Tobias Tom Date: Thu, 21 Aug 2014 11:17:08 +0200 Subject: [PATCH] Added some details about authentication handling. This details are more or less copied directly from [Authentication management in Composer](http://seld.be/notes/authentication-management-in-composer). --- .../handling-private-packages-with-satis.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/articles/handling-private-packages-with-satis.md b/doc/articles/handling-private-packages-with-satis.md index 473c4f9ed..45cfd9eb8 100644 --- a/doc/articles/handling-private-packages-with-satis.md +++ b/doc/articles/handling-private-packages-with-satis.md @@ -143,6 +143,24 @@ Example using HTTP over SSL using a client certificate: > **Tip:** See [ssl context options](http://www.php.net/manual/en/context.ssl.php) for more information. +### Authentification + +When your private repositories are password protected, you can store the authentification details permanently. +The first time Composer needs to authenticate against some domain it will prompt you for a username/password +and then you will be asked whether you want to store it. + +The storage can be done either globally in the `COMPOSER_HOME/auth.json` file (`COMPOSER_HOME` defaults to +`~/.composer` or `%APPDATA%/Composer` on Windows) or also in the project directory directly sitting besides your +composer.json. + +You can also configure these by hand using the config command if you need to configure a production machine +to be able to run non-interactive installs. For example to enter credentials for example.org one could type: + + composer config http-basic.example.org username password + +That will store it in the current directory's auth.json, but if you want it available globally you can use the +`--global` (`-g`) flag. + ### Downloads When GitHub or BitBucket repositories are mirrored on your local satis, the build process will include