Open grovesy opened 3 years ago
The developers git client uses the target GIT servers authentication/authorization mechanism - and this is pass-through/transparent to the proxy.
Therefore a Proxy user will be issued a token -
Getting a Token before working with the proxy through a git client
git remote add origin https://abc12345@gitproxy.corp.net/finos/git-proxy.git
When Clone, Pull, Push requests are made through the proxy, the proxy will take the token and tie that to the git-proxy user. The proxy will then check that the token is valid and the user is allowed to work with the repository.
I am thinking of not doing this in the short term - instead for the MVP tie the git-proxy user with the git-user
The developers git client uses the target GIT servers authentication/authorization mechanism - and this is pass-through/transparent to the proxy.
Therefore a Proxy user will be issued a token -
Getting a Token before working with the proxy through a git client
When Clone, Pull, Push requests are made through the proxy, the proxy will take the token and tie that to the git-proxy user. The proxy will then check that the token is valid and the user is allowed to work with the repository.