Git authentication for automation script


Git authentication


When you write some kind of automation (script) which needs to interact with git and clone/pull data and perform some action. And if its behind authentication layer then you need a way to automate the authentication that can let you pass credentials and automation can run without any interruption.

Either you can use ssh keys to authentication and use git@ URL to access your git repo.
But if you want to access (or force to) git via https URL you need to pass credential explicitly.
There are 2 ways to achieve this task for http protocol.



    1) Store authentication credential in the file in your home location.
Create a file under your/user's home location (.git-credentials).
$vi .git-credentials

Add following entry in the file
https://<user>:<password>@<yourserver-domain>.com

user - > user name
password -> password for the user
yourserver-domain -> your git server and domain name.

To Implement this You will need to checkout the repo first with user name and password and then run following command once.


$git config push.default simple
$git config credential.helper store

Above command will change the .git/config to accept the password from .git-credentials file now onward.

Whenever your script access the git (yourserver-domain.com), credentials will be passed for authentication via this file and will let you/script access git .

Risk 
Data stored in this file is simple text. This is flat file and you need to make sure that this file does't have permission to read by any other user. Although super user can still read it.

    2) Create a git credential cache demon
Create a file under your/user's home location (.gitconfig)
$vi .gitconfig

Add following entry in the file

[user]
        name = <ID>
        email = <Email>
[credential]
        helper = cache --timeout=36000000
[http]

[user] -> is the section for user information
name = <ID> -> is the section to provide user id
email = <Email> -> email of the user
[credential] -> this is the section which will take care of credential part
helper = cache --timeout=360000 -> this section is to cache the credential for give time (360000 seconds)
[http] - > used for http access

You have to access your git repo once and provide the credential, This configuration will take your credential and cache it in form of process for the duration of  --timeout=360000 seconds ( you can give bigger number). whenever you try to access your git server this process will take care of passing credential to git automatically.

Once process is started it will stay in memory and act as any other normal process. You will be able to see the process which will look like

$ ps -aef | grep git
user   9156     1  0 Jan05 ?        00:00:00 git-credential-cache--daemon /home/user/.git-credential-cache/socket

Benefit is that you don't need to store credential in any file in plan text format.
Once time is elapsed (or process got killed), you need to start the process again by accessing git and passing credential once again.


Comments

Post a Comment

Popular posts from this blog

Colour formatting - Jenkins Console

Image
Jenkins is the main CI tool used in Software industry. This is the backbone tool for all CI and CD implementation, Build - release and deployment methods. With the help of 100s of plugin available around the jenkins, We can achieve so much of automation around build process including build/deployment pipeline, notification, analysis, pre and post build action etc. Jenkins has tremendous power to perform great amount of work around the core build process. Many time we write script in pre and post build action to perform many tasks which is becoming very command and necessary for automation. But the main limitation in running shell script is that it's very difficult to make it more human readable for errors and make it fancy. Today i am going to cover some steps to make the output of shell script colour formatted. Jenkins Configuration Steps First install following jenkins plugin https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin Go to jenkins configurati
Read more

Manage Docker images on local disk

Docker is very powerful containerization technique, and it is becoming famous in short time. People are adapting and containerizing their applications for deployment. Soon container become very heavy and consume too much of disk space, If you do not delete old images and layers you may soon run out of disk space. Here i am trying to cover the ways to regain the disk space consumed by docker images. Moving docker filesystem to bigger mount point. Usually docker keeps all temporary files related to image building and layers at /var/lib/docker This path is local to the system usually at root partition "/" . You can mount a bigger disk space and move the content of /var/lib/docker to the new mount location and make sym link.  This way even docker images occupy space, will not affect  your system as it will be using some other mount location. Remove Old docker images Here are few ways to remove old and unused docker images Removing stopped contai
Read more

How to migrate Parent pom from maven to gradle

Convert Maven parent/super pom to Gradle init file When you think of moving to gradle for some reason from maven, You need to take care of lot of stuff around it, You can find lot of tools and help to convert maven pom.xml to gradle build.gradle But one of the most important task as an engineer or architect would be to convert your super pom (or parent pom) in to gradle init scripts. Gradle init script provides same functionality as Maven super/parent pom. The basic difference is that you can call init script Run time As many as of them This gives us flexibility to change the init script on run time but doubt of not tracking the changes.
Read more