-
Notifications
You must be signed in to change notification settings - Fork 325
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #648 from wireapp/release/20190228
- Loading branch information
Showing
240 changed files
with
1,722 additions
and
1,711 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,3 +24,6 @@ settings: | |
httpPoolSize: 1024 | ||
notificationTTL: 24192200 | ||
bulkPush: false | ||
|
||
logLevel: Info | ||
logNetStrings: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,3 +24,6 @@ settings: | |
httpPoolSize: 1024 | ||
notificationTTL: 24192200 | ||
bulkPush: false | ||
|
||
logLevel: Info | ||
logNetStrings: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,107 @@ | ||
# Rich info {#RefRichInfo} | ||
|
||
_Author: Artyom Kazak_ | ||
|
||
--- | ||
|
||
This page describes a part of the user profile called "Rich info". The corresponding feature is called "Rich profiles". | ||
|
||
## Summary {#RefRichInfoSummary} | ||
|
||
For every team user we can store a list of key-value pairs that are displayed in the user profile. This is similar to "custom profile fields" in Slack and other enterprise messengers. | ||
|
||
Different users can have different sets of fields; there is no team-wide schema for fields. All field values are strings. Fields are passed as an ordered list, and the order information is preserved when displaying fields in client apps. | ||
|
||
Only team members and partners can see the user's rich info. | ||
|
||
## API {#RefRichInfoApi} | ||
|
||
### Querying rich info {#RefRichInfoGet} | ||
|
||
`GET /users/:user/rich-info`. Sample output: | ||
|
||
```json | ||
{ | ||
"version": 0, | ||
"fields": [ | ||
{ | ||
"type": "Department", | ||
"value": "Sales & Marketing" | ||
}, | ||
{ | ||
"type": "Favorite color", | ||
"value": "Blue" | ||
} | ||
] | ||
} | ||
``` | ||
|
||
If the requesting user is not allowed to see rich info, error code 403 is returned with the `"insufficient-permissions"` error label. | ||
|
||
Otherwise, if the rich info is missing, an empty field list is returned: | ||
|
||
```json | ||
{ | ||
"version": 0, | ||
"fields": [] | ||
} | ||
``` | ||
|
||
### Setting rich info {#RefRichInfoPut} | ||
|
||
**Not implemented yet.** Currently the only way to set rich info is via SCIM. | ||
|
||
### Events {#RefRichInfoEvents} | ||
|
||
**Not implemented yet.** | ||
|
||
When user's rich info changes, the backend sends out an event to all team members: | ||
|
||
```json | ||
{ | ||
"type": "user.rich-info-update", | ||
"user": { | ||
"id": "<user ID>" | ||
} | ||
} | ||
``` | ||
|
||
Connected users who are not members of user's team will not receive an event (nor can they query user's rich info by other means). | ||
|
||
## SCIM support {#RefRichInfoScim} | ||
|
||
Rich info can be pushed to Wire by setting the `"richInfo"` field belonging to the `"urn:wire:scim:schemas:profile:1.0"` extension. Both `PUT /scim/v2/Users/:id` and `POST /scim/v2/Users/:id` can contain rich info. Here is an example for `PUT`: | ||
|
||
```javascript | ||
PUT /scim/v2/Users/:id | ||
|
||
{ | ||
..., | ||
"urn:wire:scim:schemas:profile:1.0": { | ||
"richInfo": [ | ||
{ | ||
"type": "Department", | ||
"value": "Sales & Marketing" | ||
}, | ||
{ | ||
"type": "Favorite color", | ||
"value": "Blue" | ||
} | ||
] | ||
} | ||
} | ||
``` | ||
|
||
Rich info set via SCIM can be queried by doing a `GET /scim/v2/Users` or `GET /scim/v2/Users/:id` query. | ||
|
||
### SCIM provisioning agent support {#RefRichInfoScimAgents} | ||
|
||
* Okta: unable to push fields in the format we require (checked on 2019-02-21). | ||
|
||
* OneLogin: likely able to push fields. | ||
|
||
## Limitations {#RefRichInfoLimitations} | ||
|
||
* The whole of user-submitted information (field names and values) cannot exceed 5000 characters in length. There are no limitations on the number of fields, or the maximum of individual field names or values. | ||
|
||
* Field values can not be empty (`""`). If they are empty, the corresponding field will be removed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.