From 89261487c25dba04be7ddc27c9c3edce9ea7f46a Mon Sep 17 00:00:00 2001 From: Jordan Dominion Date: Sun, 19 Mar 2023 14:55:41 -0400 Subject: [PATCH] Add InvisionCommunity to OAuth Readme --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a1fbf02bee..f6c0a9a5c3 100644 --- a/README.md +++ b/README.md @@ -164,7 +164,7 @@ Create an `appsettings.Production.yml` file next to `appsettings.yml`. This will - `Swarm:Identifier` should be set uniquely on all swarmed servers. Used to identify the current server. This is also used to select which instances exist on the current machine and should not be changed post-setup. -- `Security:OAuth:`: Sets the OAuth client ID and secret for a given ``. The currently supported providers are `Keycloak`, `GitHub`, `Discord`, and `TGForums`. Setting these fields to `null` disables logins with the provider, but does not stop users from associating their accounts using the API. Sample Entry: +- `Security:OAuth:`: Sets the OAuth client ID and secret for a given ``. The currently supported providers are `Keycloak`, `GitHub`, `Discord`, `InvisionCommunity` and `TGForums`. Setting these fields to `null` disables logins with the provider, but does not stop users from associating their accounts using the API. Sample Entry: ```yml Security: OAuth: @@ -179,10 +179,12 @@ The following providers use the `RedirectUrl` setting: - GitHub - TGForums - Keycloak +- InvisionCommunity The following providers use the `ServerUrl` setting: - Keycloak +- InvisionCommunity ### Database Configuration