-
Notifications
You must be signed in to change notification settings - Fork 355
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 #4329 from coralproject/develop
v8.5.0
- Loading branch information
Showing
109 changed files
with
3,166 additions
and
599 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,9 +35,10 @@ You will then have to generate a JWT with the following claims: | |
about status changes on a user account such as bans or suspensions. | ||
- `user.username` **(required)** - the username that should be used when being | ||
presented inside Coral to moderators and other users. There are no username validations or restrictions enforced by Coral when you're using SSO. | ||
- `user.badges` _(optional)_ - array of strings to be displayed as badges beside | ||
username inside Coral, visible to other users and moderators. For example, to indicate | ||
a user's subscription status. If you include the claim, but you are not passing a badge value, then use an empty array instead of null. | ||
- `user.badges` _(optional)_ - array of strings to be displayed as badges and custom flair badges beside username inside Coral, | ||
visible to other users and moderators. Badges are configured by passing through strings and can be used to indicate a user's subscription status. | ||
- Custom flair badges are configured by passing through names that link to the desired flair badge image. | ||
- To use custom flair badges, they must also be enabled in the admin, and each custom flair badge name, image URL must be added in the admin as well. If you include the badges claim, but you are not passing a badge value, then use an empty array instead of null. | ||
- `user.role` _(optional)_ - one of "COMMENTER", "STAFF", "MODERATOR", "ADMIN". Will create/update | ||
Coral user with this permission level. When users have both an assigned role greather than COMMENTER and a badge, both will be displayed. | ||
- `user.url` _(optional)_ - url for user account management, where a user will | ||
|
@@ -55,7 +56,8 @@ An example of the claims for this token would be: | |
"user": { | ||
"id": "628bdc61-6616-4add-bfec-dd79156715d4", | ||
"email": "[email protected]", | ||
"username": "bob" | ||
"username": "bob", | ||
"badges": ["subscriber", "https://www.example/com/image.jpg"] | ||
} | ||
} | ||
``` | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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.