habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

website/integrations: replaces all kbd and em tags (#14980)

Browse Source 
Replaces all kbd and em tags
This commit is contained in:
Dewi Roberts
2025-06-09 21:06:37 +01:00
committed by GitHub
parent dea2d67ceb
commit 856ac052e7
89 changed files with 278 additions and 277 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
website/integrations/services/truecommand/index.md
View File

@ -35,29 +35,29 @@ To support the integration of TrueCommand with authentik, you need to create an
2. Navigate to **Customization** > **Property Mappings** and click **Create**. Create create three or five **SAML Provider Property Mapping**s, depending on your setup, with the following settings:
- **Username Mapping:**
- **Name**: Choose a descriptive name
- **SAML Attribute Name**: <kbd>unique_name</kbd>
- **SAML Attribute Name**: `unique_name`
- **Friendly Name**: Leave blank
- **Expression**: <kbd>return request.user.username</kbd>
- **Expression**: `return request.user.username`
- **Email Mapping:**
- **Name**: Choose a descriptive name
- **SAML Attribute Name**: <kbd>email</kbd>
- **SAML Attribute Name**: `email`
- **Friendly Name**: Leave blank
- **Expression**: <kbd>return request.user.email</kbd>
- **Expression**: `return request.user.email`
- **Name Mapping:**
- **Name**: Choose a descriptive name
- **SAML Attribute Name**: <kbd>given_name</kbd> or <em>display_name</em>
- **SAML Attribute Name**: `given_name` or display_name
- **Friendly Name**: Leave blank
- **Expression**: <kbd>return request.user.name</kbd>
- **Expression**: `return request.user.name`
- **Title Mapping:**
- **Name**: Choose a descriptive name
- **SAML Attribute Name**: <kbd>title</kbd>
- **SAML Attribute Name**: `title`
- **Friendly Name**: Leave blank
- **Expression**: <kbd>return [custom_attribute]</kbd>
- **Expression**: `return [custom_attribute]`
- **Telephone Number Mapping:**
- **Name**: Choose a descriptive name
- **SAML Attribute Name**: <kbd>telephone_number</kbd>
- **SAML Attribute Name**: `telephone_number`
- **Friendly Name**: Leave blank
- **Expression**: <kbd>return [custom_attribute]</kbd>
- **Expression**: `return [custom_attribute]`
### Create an application and provider in authentik
@ -67,8 +67,8 @@ To support the integration of TrueCommand with authentik, you need to create an
- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later.
- **Choose a Provider type**: select **SAML Provider** as the provider type.
- **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
- Set the **ACS URL** to <kbd>https://<em>truecommand.company</em>/saml/acs</kbd>.
- Set the **Issuer** to <kbd>truecommand-saml</kbd>.
- Set the **ACS URL** to `https://truecommand.company/saml/acs`.
- Set the **Issuer** to `truecommand-saml`.
- Set the **Service Provider Binding** to `Post`.
- Under **Advanced protocol settings**, add the three or five **Property Mappings** you created in the previous section, then set the **NameID Property Mapping** to be based on the user's email. Finally, select an available signing certificate.
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.