-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Regression 19.0.6: Federation with server on which account are only local (for complete name) #24682
Labels
Comments
doc75
added a commit
to doc75/server
that referenced
this issue
Dec 13, 2020
…roperty not found Signed-off-by: Guillaume Virlet <github@virlet.org>
doc75
added a commit
to doc75/server
that referenced
this issue
Dec 13, 2020
…roperty not found Signed-off-by: Guillaume Virlet <github@virlet.org>
That seems to solve the problem!!! |
backportbot-nextcloud bot
pushed a commit
that referenced
this issue
Dec 15, 2020
…ot found Signed-off-by: Guillaume Virlet <github@virlet.org>
juliusknorr
pushed a commit
that referenced
this issue
Dec 21, 2020
…ot found Signed-off-by: Guillaume Virlet <github@virlet.org>
rullzer
added a commit
that referenced
this issue
Dec 28, 2020
[stable20] [Fix #24682]: ensure federation cloud id is retruned if FN property not found
backportbot-nextcloud bot
pushed a commit
that referenced
this issue
Jan 5, 2021
…ot found Signed-off-by: Guillaume Virlet <github@virlet.org>
Merged
juliusknorr
added a commit
that referenced
this issue
Jan 7, 2021
[stable19] [Fix #24682]: ensure federation cloud id is retruned if FN property not found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
How to use GitHub
Commit introducing this regression
Issue was certainly introduced with this commit: 16a78f5
This commit does not take into account that user setting their Full name as local will not have FN property in the trusted instances.
Steps to reproduce
Pre-requisite: You should have 2 Nextcloud instances trusting each other in terms of Federation.
occ federation:sync-addressbooks
Expected behaviour
On NC 19.0.6, I should not see the error shown below.
Tell us what should happen
Actual behaviour
On NC 19.0.5, no specific issue.
On NC 19.0.6, log is full of error message and nextcloud.log is growing rapidly (cf. log extract below)
Server configuration
Operating system: Docker official image (19-fpm)
Web server: NGINX
Database: PostgreSQL
PHP version: Docker official image (19-fpm)
Nextcloud version: 19.0.6
Updated from an older Nextcloud/ownCloud or fresh install: Updated from 19.0.5
Where did you install Nextcloud from: Docker official image (19-fpm)
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: No
Are you using encryption: yes (but only on external storage)
Are you using an external user-backend, if yes which one: No
Client configuration
Browser: Firefox
Operating system: Ubuntu 18.04
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: