Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passwordless use case? #29

Open
l3iggs opened this issue May 28, 2015 · 8 comments
Open

Passwordless use case? #29

l3iggs opened this issue May 28, 2015 · 8 comments

Comments

@l3iggs
Copy link

l3iggs commented May 28, 2015

I'd like to use this test server to setup a public repository with some lfs-server backed files that, when cloned, does not prompt the user for a user name or password to pull the lfs files (just like any old public git repository on github). Is that possible?

It would be nice if there were an environment variable that could disable authentication or something like that.

@l3iggs
Copy link
Author

l3iggs commented May 28, 2015

I would think this should be achievable by putting the user:pass in the lfs url like so:

[lfs]
    url = "https://user:pass@localhost:8080/jimdoe/lfsrepo"

But that doesn't seem to work.

@rubyist
Copy link
Contributor

rubyist commented May 28, 2015

We can make the test server work without authentication, but the client side doesn't support that very well just yet. We'll need to modify the client to only ask for authorization if the server needs it.

We don't currently support user/password in the urls store in the git config, but that may change. I think it's bad form to have the credentials checked into the repo, but it has been requested before.

@l3iggs
Copy link
Author

l3iggs commented May 28, 2015

Yeah. It's bad form for sure. I was only trying everything I can think of to get a public server working.

I'm think the "right" way to solve the problem is to have an option in the server to disable authentication and a client that respects that. I'm not holding my breath for all those changes to be made though. I had hoped I could find a way to make a public repo today.

@Yopai
Copy link
Contributor

Yopai commented Aug 15, 2015

Don't #33 and git-lfs/git-lfs#415 resolve this ?

@rubyist
Copy link
Contributor

rubyist commented Aug 17, 2015

#33 and git-lfs/git-lfs#415 only deal with the Batch API specifically. We kept it that way in the client to avoid breaking changes with the non-batched API, with the intent that in 0.6+ the Batch API will replace the other one.

@Gfurst
Copy link

Gfurst commented Feb 5, 2016

so isn't the uses:pass@server working yet?
is it a feature with git-lfs or the test server?
right that it may be bad practice to have the user name on the url to begin with, but you could have it only on your private config so don't expose but still quicken push/pulls.

@Gfurst
Copy link

Gfurst commented Feb 15, 2016

is the user@server format at least working? anyone tried that?

@jjlin
Copy link

jjlin commented Jun 23, 2016

On the latest client (1.2.1) and test server (0.3.0), I have

[lfs]
        url = "http://user:[email protected]:port/"

in my .gitconfig, and it seems to work fine. You do, of course, have to go to lfs.example.com/mgmt and add the corresponding user first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@rubyist @jjlin @l3iggs @Yopai @Gfurst and others