mirror of
https://github.com/goauthentik/authentik
synced 2026-05-05 06:32:15 +02:00
website/docs, integrations: fix language (#20338)
This commit is contained in:
@@ -38,7 +38,7 @@ To create or edit a source in authentik, open the Admin interface and navigate t
|
||||
- **User Property Mappings** and **Group Property Mappings**: Define which LDAP properties map to which authentik properties. The default set of property mappings is generated for Active Directory. See also our documentation on [property mappings](#ldap-source-property-mappings).
|
||||
|
||||
:::warning
|
||||
When the **Sync users** and or the **Sync groups** options are enabled, their respective property mapping options must have at least one mapping selected, otherwise the sync will not start.
|
||||
When the **Sync users** and/or the **Sync groups** options are enabled, their respective property mapping options must have at least one mapping selected, otherwise the sync will not start.
|
||||
:::
|
||||
|
||||
#### Additional Settings
|
||||
|
||||
@@ -34,7 +34,7 @@ To integrate Discord with authentik you will need to create an OAuth application
|
||||
- Under **Protocol Settings**:
|
||||
- **Consumer key**: set the Client ID from Discord.
|
||||
- **Consumer secret**: set the Client Secret from Discord.
|
||||
- **Scopes** _(optional)_: if you need authentik to sync guild membership information from Disord, add the `guilds guilds.members.read` scope.
|
||||
- **Scopes** _(optional)_: if you need authentik to sync guild membership information from Discord, add the `guilds guilds.members.read` scope.
|
||||
|
||||
3. Click **Save**.
|
||||
|
||||
@@ -128,7 +128,7 @@ return {
|
||||
|
||||
5. Click **Finish**.
|
||||
6. Navigate to **Directory** > **Federation and Social login** and click the **Edit** icon next to your Discord OAuth Source.
|
||||
7. Under **OAuth Attribute mapping** add the newly create property mapping to **Selected User Property Mappings**.
|
||||
7. Under **OAuth Attribute mapping** add the newly created property mapping to **Selected User Property Mappings**.
|
||||
8. Click **Update**.
|
||||
|
||||
### Checking Discord Guild membership
|
||||
@@ -188,7 +188,7 @@ return user_matched
|
||||
Ensure that the Discord OAuth source in **Federation & Social login** has the additional `guilds guilds.members.read` scopes added under **Protocol settings** > **Scopes**.
|
||||
:::
|
||||
|
||||
To check if the user is member of a Discord Guild role, you can use the following policy on your flows:
|
||||
To check if the user is a member of a Discord Guild role, you can use the following policy on your flows:
|
||||
|
||||
1. Log in to authentik as an administrator and open the authentik Admin interface.
|
||||
2. Navigate to **Customization** > **Policies**.
|
||||
|
||||
@@ -16,9 +16,9 @@ The following placeholders are used in this guide:
|
||||
|
||||
## Github configuration
|
||||
|
||||
To integrate GitHub with authentik you will need to create an OAuth application in the Discord Developer Portal.
|
||||
To integrate GitHub with authentik you will need to create an OAuth application in GitHub Developer Settings.
|
||||
|
||||
1. Log in to the GitHub and open the [Developer Settings](https://github.com/settings/developers) menu.
|
||||
1. Log in to GitHub and open the [Developer Settings](https://github.com/settings/developers) menu.
|
||||
2. Create an OAuth app by clicking on the **Register a new application** button and set the following values:
|
||||
- **Application Name**: `authentik`
|
||||
- **Homepage URL**: `www.my.company`
|
||||
@@ -29,7 +29,7 @@ To integrate GitHub with authentik you will need to create an OAuth application
|
||||
|
||||
## authentik configuration
|
||||
|
||||
To support the integration of GitHub with authentik, you need to create an GitHub OAuth source in authentik.
|
||||
To support the integration of GitHub with authentik, you need to create a GitHub OAuth source in authentik.
|
||||
|
||||
1. Log in to authentik as an administrator and open the authentik Admin interface.
|
||||
2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings:
|
||||
@@ -57,7 +57,7 @@ For instructions on embedding the new source within a flow, such as an authoriza
|
||||
Ensure that the GitHub OAuth source in **Federation & Social login** has the additional `read:org` scope added under **Protocol settings** > **Scopes**.
|
||||
:::
|
||||
|
||||
To check if the user is member of an organization, you can use the following policy on your flows.
|
||||
To check if the user is a member of an organization, you can use the following policy on your flows.
|
||||
|
||||
1. Log in to authentik as an administrator and open the authentik Admin interface.
|
||||
2. Navigate to **Customization** > **Policies**.
|
||||
@@ -111,7 +111,7 @@ return user_matched
|
||||
8. Select the policy that you previously created and click **Create**.
|
||||
9. Optionally, repeat the process for any other flows that you want the policy applied to.
|
||||
|
||||
If a user is not member of the chosen organization, they will see this message:
|
||||
If a user is not a member of the chosen organization, they will see this message:
|
||||
|
||||

|
||||
|
||||
|
||||
Reference in New Issue
Block a user