Discord OAuth2 Provider - Extended to support Guild Roles #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
https://discord.com/api/v10/users/@me/guilds/{guild.id}/member
. This API call will contain the Role IDs for a user in a given Guildtransform user
block of the Caddyfile as described in the docs added. The new roles will be in this formatdiscord.com/{$DISCORD_GUILD_ID}/role/{$DISCORD_ROLE_ID}
dicord.com/{$GUILD_ID}/members
,dicord.com/{$GUILD_ID}/admins
)dicord.com/{$GUILD_ID}/admins
Documentation PR - https://github.com/authp/authp.github.io/pull/53
Related:
Caddy Community forum post- https://caddy.community/t/caddy-security-update-for-discord-guild-role-authentication/21609