server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

also create a new user from the User Management section, called backup uploader, and from the Access Tokens section, we’ll generate a reference token associated with the user 144 Chapter 5. Devops guide that git.get_url_and_commit() will capture the url of the origin remote. This url must not encode tokens, users or passwords, for several reasons. First because that will make the process not repeatable remote -v Warning! Be aware that This method will get the output from git remote -v. If you added tokens or credentials to the remote in the URL, they will be exposed. Credentials shouldn’t be added to

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password

server authorization is done with JWT. jwt_secret is a random string used to generate authentication tokens. You can change it safely anytime (in fact it is a good practice). The change will just force users value disk_authorize_timeout is not currently used. File trans- fers are authorized with their own tokens, generated with the secret updown_secret. This value should be different from the above jwt_secret user optional arguments: -h, --help show this help message and exit -c, --clean Remove user and tokens for all remotes -p [PASSWORD], --password [PASSWORD] User password. Use double quotes if password