-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
fixed publishing of user properties to lookup-server #25300
base: master
Are you sure you want to change the base?
Conversation
Fix of the bug in the lookup_server_connector module to publish public user information to the lookup-server. As described in issue [nextcloud#25290](nextcloud#25290) Signed-off-by: AbangTor <63029179+abangtor@users.noreply.github.com>
Signed-off-by: AbangTor <63029179+abangtor@users.noreply.github.com>
Signed-off-by: AbangTor <63029179+abangtor@users.noreply.github.com>
Thanks 👍 Please squash the commits together and we are good. |
$publicData[$property->getName()] = $property->getValue(); | ||
$publicData[$property->getName()] = [ | ||
'value' => $property->getValue(), | ||
'verified' => $property->getVerified() |
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 lookup server also seems to check a signature at least for Twitter and website?
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.
Mind to add how to get the signature? We talked briefly about the signature at #25290 and were lost ;)
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.
Seems good to me.
Still not fixed in 2023. |
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.
Seems good to me too.
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.
Seems good to me too.
Signed-off-by: John Molakvoæ <skjnldsv@users.noreply.github.com>
@ArtificialOwl you're our expert in lookup server, could you have a look when time allows? :) |
Reopening to review. Anything here that still needs to be done @abangtor ? We would like to help you get this one in :) |
Fix #25290
Fix of the bug in the lookup_server_connector module to publish public user information to the lookup-server.
There is a bug in the getUserAccountData method in the RetryJob.php of the lookup-server-connector module.
The properties are written into an one dimensional array $publicData:
server/apps/lookup_server_connector/lib/BackgroundJobs/RetryJob.php
Line 197 in 7668c86
Later on the array is read as it is a two dimensional array:
server/apps/lookup_server_connector/lib/BackgroundJobs/RetryJob.php
Lines 203 to 214 in 7668c86
This causes the values to be empty and no properties are send to the loopup-server.