205hlab-mirrors/authentik
2
0
Fork 0
mirror of https://github.com/goauthentik/authentik.git synced 2026-06-17 19:09:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

website/integrations: FortiManager: cleanup (#23110)

Browse Source 
Agent-thread: https://sdko.org/internal/thr/ak/019eccfc-d6c2-7df3-ae39-4a4bd262c174

A7k-product: product

A7k-product-repo: 3

Co-authored-by: Agent <gptagent@svc.sdko.net>
This commit is contained in:
Dominic R
2026-06-16 06:47:21 -04:00
committed by GitHub
parent 720e819277
commit 150df63432
1 changed files with 57 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/integrations/networking/fortimanager/index.md
+57 -20
View File
@@ -18,43 +18,80 @@ The following placeholders are used in this guide:
- `authentik.company` is the FQDN of the authentik installation.
:::info
This documentation only lists the settings that have been changed from their default values. Please verify your changes carefully to avoid any issues accessing your application.
This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application.
:::
## authentik configuration
To support the integration of FortiManager with authentik, you need to create an application/provider pair in authentik.
To support the integration of FortiManager with authentik, you need to create a SAML property mapping and an application/provider pair in authentik.
### Create a property mapping in authentik
FortiManager expects a SAML attribute named `username` that contains the value used to identify the administrator account. This example uses the authentik username, but you can return any user attribute that matches the FortiManager administrator identifier.
1. Log in to authentik as an administrator and open the authentik Admin interface.
2. Navigate to **Customization** > **Property Mappings** and click **Create**.
3. Select **SAML Provider Property Mapping** as the type and click **Next**.
4. Create a property mapping with the following values:
- **Name**: `FortiManager username`
- **SAML Attribute Name**: `username`
- **Expression**:
```python
return request.user.username
```
5. Click **Finish** to save the property mapping.
:::info Optional SAML attributes
FortiManager also accepts `profilename` and `adoms` attributes. The `profilename` attribute assigns a matching admin profile that already exists on FortiManager. The `adoms` attribute grants access to one or more administrative domains (ADOMs). To use either attribute, create additional SAML provider property mappings with the corresponding **SAML Attribute Name**, return the desired values from the **Expression**, and add the mappings to **Selected User Property Mappings** when configuring the provider.
:::
### Create an application and provider in authentik
1. Log in to authentik as an administrator and open the authentik Admin interface.
2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard.
- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
- **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 `https://fortimanager.company/saml/?acs`.
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Note the **Slug** value because you will use it when configuring FortiManager.
- **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 `https://fortimanager.company/saml/?acs`.
- Set the **SLS URL** to `https://fortimanager.company/saml/?sls`.
- Under **Advanced protocol settings**:
- Set the **Signing Certificate** to any available certificate.
- Add `FortiManager username` to **Selected User Property Mappings**.
- Set the **NameID Property Mapping** to `authentik default SAML Mapping: Username`.
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **Application Dashboard** page.
3. Click **Submit** to save the new application and provider.
## FortiManager configuration
1. Navigate to `https://fortimanager.company/p/app/#!/sys/sso_settings` and select **SAML SSO Settings** to configure SAML.
2. Under **Single Sign-On Mode**, choose **Service Provider (SP)** to enable SAML authentication.
3. Set the **SP Address** field to the FortiManager FQDN, `fortimanager.company`. This provides the URLs needed for configuration in authentik.
4. Choose the **Default Login Page** as either **Normal** or **Single Sign-On**. Selecting **Normal** allows both local and SAML authentication, while **Single Sign-On** restricts login to SAML only.
5. By default, FortiManager creates a new user if one does not exist. Set the **Default Admin Profile** to assign the desired permissions to new users. A `no_permissions` profile is created by default for this purpose.
6. Set the **IdP Type** field to **Custom**.
7. For the **IdP Entity ID** field, enter: `https://authentik.company/application/saml/<application_slug>/metadata/`
8. Set the **IdP Login URL** to: `https://authentik.company/application/saml/<application_slug>/`
9. Set the **IdP Logout URL** to: `https://authentik.company/`
10. In the **IdP Certificate** field, import your authentik certificate (either self-signed or valid).
1. Log in to the FortiManager web interface as an administrator.
2. Navigate to **System Settings** > **SAML SSO**.
3. Configure the **Single Sign-On Settings**:
- **Server Address**: `fortimanager.company`
- **Single Sign-On Mode**: `Service Provider (SP)`
- **SP Certificate**: select an available certificate.
- **Default Login Page**: select whether FortiManager should show the normal login page with an SSO option, or redirect directly to authentik.
- **Auto Create Admin**: enable this setting if FortiManager should create SSO administrators on first login. If you leave it disabled, create matching SSO administrators in FortiManager before testing the integration.
4. Configure the **IdP Settings**:
- **IdP Type**: `Custom`
- **IdP Entity ID**: `https://authentik.company/application/saml/<application_slug>/metadata/`
- **IdP Login URL**: `https://authentik.company/application/saml/<application_slug>/`
- **IdP Logout URL**: `https://authentik.company/application/saml/<application_slug>/`
- **IdP Certificate**: import the signing certificate that you selected in the authentik SAML provider. You can download it from the authentik SAML provider page, under **Related objects** > **Download signing certificate**.
5. If you enabled any options under **Signing Options** in FortiManager, align them with the corresponding options under **Advanced protocol settings** in the authentik SAML provider.
6. Click **Apply** to save the configuration.
:::info Administrator permissions
With **Auto Create Admin** enabled, newly-created SSO administrators receive the configured default admin profile. If users should receive permissions through SAML attributes instead, create matching FortiManager admin profiles and administrative domains, and send the optional `profilename` and `adoms` attributes from authentik.
:::
## Configuration verification
To confirm that authentik is properly configured with FortiManager, log out and log back in via authentik.
To confirm that authentik is properly configured with FortiManager, open FortiManager and sign in via authentik.
## Resources
- [Community post on the Fortinet forum](https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-Configure-SAML-SSO-login-with-Azure-AD/ta-p/198324)
- [FortiManager Administration Guide - SAML admin authentication](https://docs.fortinet.com/document/fortimanager/8.0.0/administration-guide/981386/saml-admin-authentication)
- [FortiManager CLI Reference - SAML](https://docs.fortinet.com/document/fortimanager/8.0.0/cli-reference/91498/saml)