-
-
Notifications
You must be signed in to change notification settings - Fork 989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
website/integrations: all general cleanup and updates #12716
base: main
Are you sure you want to change the base?
Conversation
Update integrations: Apache Guacamole, ArgoCD, Arube Orchestrator
✅ Deploy Preview for authentik-storybook canceled.
|
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12716 +/- ##
==========================================
- Coverage 92.70% 92.70% -0.01%
==========================================
Files 769 769
Lines 38898 38898
==========================================
- Hits 36062 36060 -2
- Misses 2836 2838 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: 4d62 <[email protected]>
Co-authored-by: Tana M Berry <[email protected]> Signed-off-by: 4d62 <[email protected]>
7. For the **IdP Entity ID** field, enter: `https://authentik.company/application/saml/fortimanager/sso/binding/redirect/` | ||
8. Set the **IdP Login URL** to: `https://authentik.company/application/saml/fortimanager/sso/binding/redirect/` | ||
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Needs clarification of where it can be found and how it's configured
2. Under **Single Sign-On Mode**, choose **Service Provider (SP)** to enable SAML authentication. | ||
3. Set the **SP Address** field to the FortiManager FQDN, <kbd>fortimanager.company</em>. 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Where is that no_permissions profile, what is it, how? IDK
sdko/integration-batch-updates/a
internal task: AUTH-914
Progress