-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add nextcloud provider #179
Conversation
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.
@Ramblurr Thanks for adding this support. I'm happy for us to support this but as I have no way to test this, could you please add yourself to the CODEOWNERS file taking ownership of the relevant files. This way if there are any issues with it, people should be able to ping you?
Thanks for the review. I'm leaving for vacation soon, so I'll get back to this in several weeks. |
cb35219
to
2766b07
Compare
2766b07
to
945fdef
Compare
945fdef
to
b174d0d
Compare
I'm back at this again, sorry for the delay @JoelSpeed. I rebased and patched my PR given the recent shakeup for 4.0.0, and I've made the requested changes. The Travis build is failing due to a linting error in code I didn't touch:
This is code in If I disable linting and run just the tests, they pass fine locally. |
|
Should I add that as a commit to this PR? |
In the function } else if r.Header.Get("Authorization") != "Bearer imaginary_access_token" { and that is what caused this dumb linter rule to be triggered. So to quiet the rule, you can change your tests to use a different mock access token string. |
b174d0d
to
ceda9d3
Compare
ceda9d3
to
cd98969
Compare
Oh! I see, the linter is comparing the strings across the entire project. Sorry about that. That explains why this isn't present on master :) Pushed the fix. |
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.
Added a few tiny nits (sorry).
Are you ok to add yourself to the CODEOWNERS for this provider? Totally optional of course 😄
cd98969
to
b40d224
Compare
fixed!
If you're referring to .github/CODEOWNERS, then I've already added myself there :) |
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.
LGTM 👍
This has been open for a while so let's get the changelog conflicts resolved and we can merge. @JoelSpeed: if you've time to re-review then that would be great! |
b40d224
to
4b21054
Compare
Fixed the CHANGELOG conflict. |
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.
Thank you and congrats on your first contribution! 🎉
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.
One quick question about the docs, I may not be understanding fully though
docs/2_auth.md
Outdated
-provider nextcloud | ||
-client-id <from nextcloud admin> | ||
-client-secret <from nextcloud admin> | ||
-login-url="<your gitlab url>/index.php/apps/oauth2/authorize" |
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.
Should this be gitlab
or nextcloud here? Looks like maybe a copy paste error?
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.
Woops, you are right. Should definitely be nextcloud.
e9f209f
to
ab8af5b
Compare
ab8af5b
to
227ea5d
Compare
Fixed doc typo and rebased master. |
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.
The changelog entry is in the wrong place right now but I'll fix that up later, thanks @Ramblurr for being patient with us!
Co-authored-by: Xunzhuo <bitliu@tencent.com>
…re/bumpredischart Bump redis chart version
Description
This PR adds the Nextcloud provider, that allows for authentication of users on a Nextcloud instance.
Motivation and Context
For some time now Nextcloud has had an Oauth2 implementation that allows for arbitrary 3rd party tools to act as oauth2 clients and perform authentication for users hosted on the Nextcloud instance.
Docs: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/oauth2.html
How Has This Been Tested?
Checklist