-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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/docs: Add Fleet integration. #13618
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 site configuration. |
✅ Deploy Preview for authentik-storybook canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #13618 +/- ##
==========================================
+ Coverage 91.73% 92.76% +1.03%
==========================================
Files 794 794
Lines 40502 40525 +23
==========================================
+ Hits 37156 37595 +439
+ Misses 3346 2930 -416
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
authentik PR Installation instructions Instructions for docker-composeAdd the following block to your AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-d031bb05a98c190fbe637121e69ee789db5645f1
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s Afterwards, run the upgrade commands from the latest release notes. Instructions for KubernetesAdd the following block to your authentik:
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
global:
image:
repository: ghcr.io/goauthentik/dev-server
tag: gh-d031bb05a98c190fbe637121e69ee789db5645f1 Afterwards, run the upgrade commands from the latest release notes. |
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.
Wow looks great, thank you @teffen! I made a few edits; let me know if you want to try and get this merged tonight.
Co-authored-by: Tana M Berry <[email protected]> Signed-off-by: Teffen Ellis <[email protected]>
Signed-off-by: Teffen Ellis <[email protected]>
|
||
By the end of this integration, your users will be able to log into Fleet using their authentik credentials. | ||
|
||
Your authentik and Fleet instance must both be running and accessible on an HTTPS domain. |
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.
Your authentik and Fleet instance must both be running and accessible on an HTTPS domain. | |
Your authentik and Fleet instances must both be running and accessible on an HTTPS domain. |
|
||
2. For the **App name** enter `Fleet` and click **Next**. | ||
|
||
3. Choose **SAML** as the **Provider Type** and click **Next**. |
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.
You can delete this line... it's a dupe of Step 4, on line 43, no? Sorry I missed that earlier!
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.
Thanks @GirlBossRush! Two more things, both of which I missed on first pass, sorry!
Details
This PR adds a guide for Fleet Device Management
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 website
)