website: Bump prettier from 3.3.3 to 3.4.1 in /website (#12205)
* website: Bump prettier from 3.3.3 to 3.4.1 in /website Bumps [prettier](https://github.com/prettier/prettier) from 3.3.3 to 3.4.1. - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](https://github.com/prettier/prettier/compare/3.3.3...3.4.1) --- updated-dependencies: - dependency-name: prettier dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * update formatting Signed-off-by: Jens Langhammer <jens@goauthentik.io> * sigh Signed-off-by: Jens Langhammer <jens@goauthentik.io> * disable flaky test Signed-off-by: Jens Langhammer <jens@goauthentik.io> --------- Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Jens Langhammer <jens@goauthentik.io> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
dependabot[bot]
@ -18,10 +18,10 @@ sidebar_label: FortiGate Admin Login
|
||||
|
||||
The following placeholders will be used:
|
||||
|
||||
- `fgt.company` is the FQDN of the FortiGate install.
|
||||
- `authentik.company` is the FQDN of the authentik install.
|
||||
- `fgt.mapping` is the name of the SAML Property Mapping.
|
||||
- `ak.cert` = The authentik self-signed certificate you use for the service provider.
|
||||
- `fgt.company` is the FQDN of the FortiGate install.
|
||||
- `authentik.company` is the FQDN of the authentik install.
|
||||
- `fgt.mapping` is the name of the SAML Property Mapping.
|
||||
- `ak.cert` = The authentik self-signed certificate you use for the service provider.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you have changed the port of the admin login from 443 to anything else you have to append it behind `fgt.company`. So f.e. `fgt.company:10443`.
|
||||
@ -30,37 +30,37 @@ The following placeholders will be used:
|
||||
|
||||
Create a new SAML Property Mapping under the Customization settings.
|
||||
|
||||
- `fgt.mapping` is the value for the Name.
|
||||
- `username` is the value for the SAML Attribute Name.
|
||||
- `return request.user.email` is the value for the Expression.
|
||||
- `fgt.mapping` is the value for the Name.
|
||||
- `username` is the value for the SAML Attribute Name.
|
||||
- `return request.user.email` is the value for the Expression.
|
||||
|
||||
Create an application and SAML provider in authentik, and note the slug, because this will be used later. Create a SAML provider with the following parameters:
|
||||
|
||||
Provider:
|
||||
|
||||
- ACS URL: `https://fgt.company/saml/?acs`
|
||||
- Issuer: `https://authentik.company`
|
||||
- Service Provider Binding: Post
|
||||
- Audience: `https://fgt.company/metadata/`
|
||||
- Signing Certificate: `ak.cert`
|
||||
- Property mappings: `fgt.mapping`
|
||||
- ACS URL: `https://fgt.company/saml/?acs`
|
||||
- Issuer: `https://authentik.company`
|
||||
- Service Provider Binding: Post
|
||||
- Audience: `https://fgt.company/metadata/`
|
||||
- Signing Certificate: `ak.cert`
|
||||
- Property mappings: `fgt.mapping`
|
||||
|
||||
You can of course adjust durations.
|
||||
|
||||
Application:
|
||||
|
||||
- Name: `Fortigate`
|
||||
- Slug: `fortigate`
|
||||
- Launch URL: `https://fgt.company/`
|
||||
- Name: `Fortigate`
|
||||
- Slug: `fortigate`
|
||||
- Launch URL: `https://fgt.company/`
|
||||
|
||||
## FortiGate Configuration
|
||||
|
||||
Navigate to `https://fgt.company/ng/system/certificate` and Import the Certificate `ak.cert` to the FortiGate.
|
||||
Then navigate to `https://fgt.company/fabric-connector/edit/security-fabric-connection` and select `Single Sign-On Settings` to configure SAML.
|
||||
|
||||
- Select `Service Provider (SP)` under Mode to enable SAML authentication.
|
||||
- Set the `SP Address` to the FortiGate FQDN `fgt.company`. (This gives you the URLs to configure in authentik)
|
||||
- Set the `Default Login Page` to either `Normal` or `Single-Sign On`. (Normal allows both local and SAML authentication vs only SAML SSO.)
|
||||
- Select `Service Provider (SP)` under Mode to enable SAML authentication.
|
||||
- Set the `SP Address` to the FortiGate FQDN `fgt.company`. (This gives you the URLs to configure in authentik)
|
||||
- Set the `Default Login Page` to either `Normal` or `Single-Sign On`. (Normal allows both local and SAML authentication vs only SAML SSO.)
|
||||
|
||||
FortiGate creates a new user by default if one does not exist, so you will need to set the Default Admin Profile to the permissions you want any new users to have. (I have created a `no_permissions` profile to assign by default.)
|
||||
|
||||
@ -69,11 +69,11 @@ Under `SP Details` set the **SP entity ID** to `https`. Note it for later use (t
|
||||
> [!IMPORTANT]
|
||||
> On both `IdP Login and Logout URL` change the `<SLUG>` to your own from the authentik application you have created.
|
||||
|
||||
- Set `IdP Type` to `Custom`
|
||||
- Set `IdP entity ID` to `https://authentik.company`
|
||||
- Set `IdP Login URL` to `https://authentik.company/application/saml/<SLUG>/sso/binding/redirect/`
|
||||
- Set `IdP Logout URL` to `https://authentik.company/application/saml/<SLUG>/slo/binding/redirect/`
|
||||
- Set `IdP Certificate` to `ak.cert`
|
||||
- Set `IdP Type` to `Custom`
|
||||
- Set `IdP entity ID` to `https://authentik.company`
|
||||
- Set `IdP Login URL` to `https://authentik.company/application/saml/<SLUG>/sso/binding/redirect/`
|
||||
- Set `IdP Logout URL` to `https://authentik.company/application/saml/<SLUG>/slo/binding/redirect/`
|
||||
- Set `IdP Certificate` to `ak.cert`
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
Reference in New Issue
Block a user