release-engineering/dist-git
1
0
Fork 0
mirror of https://github.com/release-engineering/dist-git.git synced 2025-02-23 15:02:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Adam Samalik 2015-04-10 10:20:23 +02:00
parent 53b93e76d1
commit 92ac1b4cbe
1 changed files with 14 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -47,5 +47,17 @@ The following is an example JSON data comming from the Package Database which wo
``` ```
The final result would consist of two package repositories: The final result would consist of two package repositories:
- *copr-frontend* with branches *master* and *fedora-21* - *copr-frontend* with a single branch: *fedora-21*
- *copr-backend* with three branches *master*, *fedora-21* and *centos-7* - *copr-backend* with two branches: *fedora-21* and *centos-7*
### Client Authentication and Authorization
In order to make changes in the package repositories, client needs to have a permission to do that. Both Git and Lookaside Cache have their own auth process.
Git uses ssh communication and client authenticates with public key. Each user needs to have an account on the server and be in a *packager* group. Their ssh shell must be set to "`HOME=/var/lib/dist-git /usr/share/gitolite3/gitolite-shell %(username)s`" in order to have authorization working.
Authorization is done by Gitolte. The configuration file describing all the permisions is automaticaly generated each time a Package Database is queried. Gitolite uses system users and groups.
Lookaside Cache uses https communication and client authenticates with ssl client certificate. The Dist Git service provider needs to issue the client certificate for every user.
There is no authentication needed in order to read from the server.