-
-
Notifications
You must be signed in to change notification settings - Fork 571
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
Nextcloud login not working (not using configured server address) #3214
Comments
I also tried putting that config into my # ...
SOCIALACCOUNT_PROVIDERS='{ "nextcloud": { "APPS": [ { "client_id": "#REDACTED", "secret": "#REDACTED", "settings": { "server": "https://my-redacted-nextcloud-address/", } } ] }}' But it results in the exact same behavior |
don't enclose it in quotes |
I removed the quotes like this: SOCIALACCOUNT_PROVIDERS={ "nextcloud": { "APPS": [ { "client_id": "#REDACTED", "secret": "#REDACTED", "settings": { "server": "https://my-redacted-nextcloud-address/" } } ] }} But I still get thrown to |
and you rebuilt the container after making the change? |
Yes, I rebuilt the container with |
can you remove the trailing slash in the url configuration? if that doesn't work I'd suggest joining the discord and see if anyone has a working configuration. |
This works for me: |
Doing this in addition to configuring the provider inside of the Django admin panel (while leaving the |
Here's where the new structure was introduced: https://docs.allauth.org/en/latest/release-notes/recent.html#id49 |
Thx for the tip, using
worked for me. Next up is figuring out the redirect URL to be entered in Nextcloud... |
|
Issue
I'm trying to add login via Nextcloud to my Tandoor instance. I enabled the Nextcloud provider in my
.env
file viaand configured a new Social Application via the Django admin. I added the client ID and secret and added the following text to the Settings input:
But when I click Sign in using Nextcloud and then Continue, I always get redirected to
https://nextcloud.example.org/
instead ofhttps://my-redacted-nextcloud-address/
. It seems that Tandoor/django-allauth doesn't respect theSERVER
field inside the settings ashttps://nextcloud.example.org/
is the default fallback value. Am I misunderstanding the configuration process or is this a bug?Tandoor Version
1.5.18
OS Version
Debian 12.6
Setup
Docker / Docker-Compose
Reverse Proxy
Others (please state below)
Other
nginx (Plain old nginx, not nginx proxy manager)
Environment file
Docker-Compose file
Relevant logs
No response
The text was updated successfully, but these errors were encountered: