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

Use OIDC to authenticate to keycloak instead of fix username and password #328

Closed
bitvilag opened this issue Nov 17, 2022 · 3 comments
Closed

Comments

@bitvilag
Copy link

I currently use keycloak as user backend using the OIDC protocol and I am moving the nextcloud instance to this as well. I was wondering if you ever tried to interact with nextcloud using tokens creating a personal account/space for the user?

@perry-mitchell perry-mitchell transferred this issue from perry-mitchell/webdav-fs Nov 21, 2022
@perry-mitchell
Copy link
Owner

Hi @bitvilag - I moved this to the base repo, where such a feature would be implemented.

I'm not sure I understand what you're asking - Wouldn't such a setup still result in something like a token? This library isn't so much concerned about the authentication flow as it is about WebDAV interoperability.

Basically: could you kindly elaborate as to what you would expect this library to have implemented to support your way of working?

@bitvilag
Copy link
Author

Dear @perry-mitchell,

I am still on the "figuring out" phase, but I also looked into a different library and asked the same question: tentwentyfour/nextcloud-link#54

There, I elaborate a bit better on the use-case.

@perry-mitchell
Copy link
Owner

I'm going to close this for now. If this gets fleshed out a bit more I'll happily reopen. Thanks.

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

2 participants