-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Avatar privacy and new scope #26243
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
Avatar privacy and new scope #26243
Conversation
d728469 to
023db70
Compare
|
0ee96fa to
5512c24
Compare
|
Updated top post to also extend the OCS API endpoint to allow clients to get/set scope values |
|
hah... it appears that the provisioning API is also cheating and using AccountManager->getUser(), so the mapping will not work there. I'll migrate it to use |
|
OCS API has been adjusted. Next up: unit tests |
bc533b8 to
a7134e0
Compare
|
unit tests done next up would be fixing guest avatar performance, but could also be done separately as the current approach already works however, still need to settle at least on wording and icons |
|
Added task "add capability". I think a simple boolean should do to signal the ability to read and set scopes. |
|
|
Added capability: Added |
|
Earn bonus points for expanding https://github.com/nextcloud/server/blob/master/build/integration/features/provisioning-v1.feature |
done |
nickvergessen
left a comment
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.
Wording and icons to discuss, but works technically
Added new v2-private account manager scope that restricts the scope further by excluding public link access. Avatars with v2-private account scope are now showing the guest avatar instead of the real avatar. Signed-off-by: Vincent Petry <[email protected]>
Now not all fields have the "v2-private" option in place. Fix dropdown issue when a scope was stored that is not listed after disabling the lookup server. Whenever the lookup server upload is disabled, the scope menu is now displayed where it makes sense to allow switching between the two private scopes. Signed-off-by: Vincent Petry <[email protected]>
Use new scope values in settings page. Adjust all consumers to use the new constants. Map old scope values to new ones in account property getter. Signed-off-by: Vincent Petry <[email protected]>
The fields for phone number, address, website and twitter are now editable regardless whether federated sharing and the lookup server are enabled or not. Signed-off-by: Vincent Petry <[email protected]>
Extends the provisioning API to allow a user to get and set their own account property scopes. Signed-off-by: Vincent Petry <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
When avatar scope is private, the PlaceholderAvatar is used to deliver a placeholder avatar based on the user's initials. This was implemented as a separate class for now to avoid messing with the existing UserAvatar implementation and its generated vs non-generated logic. Signed-off-by: Vincent Petry <[email protected]>
Include version number in capability Signed-off-by: Vincent Petry <[email protected]> Co-authored-by: Joas Schilling <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
Added integration tests for the scope attributes in the provisioning API. Signed-off-by: Vincent Petry <[email protected]>
Signed-off-by: Vincent Petry <[email protected]>
c1668fa to
5a8b7c1
Compare
|
rebased for CI |
Added additional capability in the provisioning API to signal whether the federation scope values can be used. This is based on whether the lookup server upload is enabled or not. Signed-off-by: Vincent Petry <[email protected]>
|
|
|
can someone force merge maybe ? seems the notifications app might be cached or something... in any case, the test failure is unrelated |
|
/backport to stable21 |
Todos
Issues