nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LFS repeat logon?

unknown

I'm getting prompted to authenticate repeatedly when cloning a repo with LFS managed content - one password prompt for each LFS managed file in the repo. I'm guessing that this is because the LFS managed files are via SSH and the rest are via HTTP(S).

Any way to prevent multiple prompts? Makes this pretty useless for automated purposes (build, deploy etc) otherwise.

Accepted answers

Felix_qq95eu

Hi @David X Johnson,

for LFS it is recommended to use Git's Credential Storage caching. This means that you'll only need to enter your credentials once.

You can set credential caching in your git config by running the following command:

git config --global credential.helper cache

I hope that helps,

Felix

All comments

Felix_qq95eu

Hi @David X Johnson,

for LFS it is recommended to use Git's Credential Storage caching. This means that you'll only need to enter your credentials once.

You can set credential caching in your git config by running the following command:

git config --global credential.helper cache

I hope that helps,

Felix

Ben Humphreys

Hi David,

This is a common question and relates to how the client is implemented as a Git filter, see: https://github.com/github/git-lfs/issues/858

During clone, the git filter is invoked once per LFS file, which is likely why you are seeing a password (or SSH passphrase) request for each file.

The recommendation is to setup a credentials cacher. Your question seems to indicate you are using an SSH remote, and while it is true that the actual LFS traffic will be via HTTP/HTTPS what you actually need is something like ssh-agent to cache your SSH passphrase. The configuration of such a cache will vary depending on your operating system.

The authentication process is different for SSH vs HTTP remotes:

SSH Remotes: When an SSH remote is used Bitbucket Server will respond to the git-lfs-authenticate command and will supply an authentication token that the Git LFS client will then be used to access the Git LFS API via HTTP/HTTPS. In this case you will be prompted for your SSH key passphrase.

HTTP/S Remotes: When a HTTP/S remote is used the client making a request of Bitbucket Server will be required to provide a username and password for basic auth.

Hope this helps.

Regards,
Ben

unknown

Thank you, this was the solution I was looking for.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

bitbucket-administration