-
Notifications
You must be signed in to change notification settings - Fork 311
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
Simple Auth support #345
Simple Auth support #345
Conversation
Hi @ktaletsk, thanks for this, I'm looking exactly for this! |
@saulshanabrook, is there any update on this PR? Do you have any questions regarding proposed changes? I would rebase to the latest 0.6.0, but I need to know if this PR will be considered. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay on this, thank you for contributing this feature! It looks good to me.
I am going to resolve all the current conflicts with master shortly |
I don't think this question from Saul was addressed, and I have the same question. |
Per @saulshanabrook,
Should I take commit author attribution out of this Auth PR and submit as a separate PR? |
That would be ideal, but I understand it's more work for you. I am OK taking this as is, but @jaipreet-s would you prefer them to be split? |
15b7982
to
b88c2e5
Compare
@saulshanabrook @jaipreet-s I removed my implementation of the identity feature as it was added by #366. I also rebased to the latest master. Please, take a look. |
Thank you @fcollonval for the review and useful suggestions. I addressed the issues in the latest commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx @ktaletsk
This is a great addition!
@ktaletsk I forgot to point out, you need to add Lines 17 to 20 in 0b4339f
@jaipreet-s @saulshanabrook I think this is now ready to be merged. Could you please have a look? |
Thanks @ktaletsk for this work! I'll attempt to take a look sometime next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! I have some feedback but once that is addressed it would be great to have this feature merged in :-)
@jaipreet-s @fcollonval I went through the latest review, but I couldn't find a way to make the username and password required fields. Do you have any suggestions how to implement that? |
@ktaletsk Could you please rebase your branch on the master to solve the conflicts? |
43ca3fd
to
f63c65c
Compare
@fcollonval rebased! Let's merge it |
Thx a lot @ktaletsk especially for your patience to bring it through all the comments. |
Changes have been taken into account
Thanks @fcollonval @jaipreet-s @saulshanabrook and everyone who participated in discussions. Feels great to contribute to this extension! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
In which release this change is going to be included? I can see 0.8.1 as latest (https://pypi.org/project/jupyterlab-git/) |
There is no release containing this feature yet. You can watch for new
release to be notified.
Le jeu. 17 oct. 2019 à 06:55, sudeshgit <[email protected]> a écrit :
… In which release this change is shipped? I can see 0.8.1 as latest (
https://pypi.org/project/jupyterlab-git/)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#345?email_source=notifications&email_token=ACALK72D3DRFCVDIIYMU3NTQO7V3FA5CNFSM4HJQATW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBOYWMA#issuecomment-543001392>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACALK7Z7OLOD6CKIZN7M5H3QO7V3FANCNFSM4HJQATWQ>
.
|
Adds simple credentials support as requested in #299
User flow
3a. If wrong credentials are provided form is shown over and over until successful authentication / or until user clicks 'CANCEL' button on the credentials form.
If user sets their own credentials, step 3 never happen.
When cloning/pulling from public repo, step 3 never happen
Technical details
On the backend, API handler is overloaded to expect auth information.
Git
class methodsclone
,push
andpull
are updated to allow passing of username/password information to git CLI using pexpect library similar to howsubprocess.Popen
is used to do that without credentials.On the frontend, couple of new forms are added.
src/components/CredentialsBox.tsx
implements the body of credentials dialog.src/components/CommitAuthorBox.tsx
implements similar dialog, but for author information on git commit.Comments
UI is still little rough around the edges, but I hope community can help me fix that.