-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
website/integrations: KnowBe4 #17899
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-storybook canceled.
|
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #17899 +/- ##
==========================================
+ Coverage 92.82% 92.87% +0.04%
==========================================
Files 869 869
Lines 48040 48040
==========================================
+ Hits 44591 44615 +24
+ Misses 3449 3425 -24
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Details
Kept the SAML integration streak going with a KnowBe4 guide. The doc covers both sides:
I also added a recovery note about the Bypass-SSO URL (for the MFA bypass option) and a verification checklist so admins can test the full redirect loop.
In this case it is more usefull to configure KnowBe4 prior to authentik.
Checklist
ak test authentik/)make lint-fix)If an API change has been made
make gen-build)If changes to the frontend have been made
make web)If applicable
make docs)