-
Notifications
You must be signed in to change notification settings - Fork 44
Username and password not working for private template source #3153
Comments
Thanks for raising this, it looks like I didn't add it originally because the implementation is slightly different to GHE, and at the time the spec was only GHE. (Although I did make We are seeing 404 because PFE does not validate credentials before GETing the devfile. I guess GitHub returns 404 rather than 401 to GET requests for files when given incorrect credentials. (By contrast, GitHub returns 401 to requests to clone a repo when given incorrect credentials - which is why If we need to support private GH template repos I can add it - @tobespc do we need to? |
As for GHE, that should be working. Does I'm happy to debug with you if that helps |
Re supporting private GH repos, I have confirmed with @tobespc that it is still not part of the spec for now |
@tobespc @tetchel @eharris369 are we iceboxing this or resolving it? |
still waiting to hear back from icp4a |
It does not seem to work for me on GHE either. I tried GETing that URL while logged in using the HTTP client I use in the VS Code plugin too and also got a 404. So it may be a quirk of the IBM SSO wrapping the GHE authentication (eg, if I try and log into a private window with that username/password I get a 2FA prompt); basic auth may not be sufficient. |
supporting private template sources is out of scope for codewind with the current requirements. Moving to icebox |
do you mean private github repos? they still work with access tokens |
It probably is due to SSO: https://developer.github.com/v3/auth/ Also, according to that document, github is removing api auth using username/password later this year. I think we should leave the ability to use username/password in codewind, since template sources could be hosted at sites other than github and those sites could use username/password authentication. |
@tetchel hmm I don't know why it's not working for you on GHE. At least 2 members of Portal besides me have managed to access that GHE template repo using their GHE creds, which for them is their IBM intranet password |
Do any of those people have 2fa enabled on ghe? Basically, we need to come up with a support statement. We support github public in these cases, and github private in these cases. I suppose basic auth (username/pw) should still work in theory for an arbitrary webserver that accepted it and gave the expected status codes, too. |
@jopit @tetchel |
To summarize what I have seen:
I'm still not certain if 2fa is the breaker here; I just know Erin and I have it on and it does not work for us, but has been reported to work for some others (#3153 (comment)) so that is my best guess. Jag, in your comment above, did you have 2fa enabled on those accounts? edit: jag did not have 2fa enabled, so I'm not sure why credentials worked for some. Removed 2fa from the table. |
The username and password are never checked for public repos. So you can enter any bogus username and password, or none, and public repos will still work. |
I can't get my username/password to work with a public github private repository. @eharris369 tried too on GHE and had the same result. PATs work, though.
Also, cwctl should exit with a failure code in this case.
The text was updated successfully, but these errors were encountered: