authenticationauthentikauthorizationkubernetesoauth2oauth2-clientoauth2-serveroidcoidc-clientoidc-providerproxyreverse-proxysamlsaml-idpsaml-spsecuritysso
a3673906c7
This commit implements a three-tier sidebar with subcategories. The first thing is that we've refactored the Sidebar into a holistic entity; rather than be built in pieces, it's constructed declaratively from a tree of entries, much in the same way routes are, and for much the same reason<sup>1</sup>. The AdminSidebar element only provides the list of entries to show and some of the controls necessary to show/hide the sidebar. Because the sidebar requires a rich collection of objects retrieved from the back-end, to avoid cluttering the AdminSidebar each of those sublists of TypeCreate have been isolated into their own controllers. The SidebarTypeController isn't even a strongly reactive controller; all it does is fetch the TypeCreate collection and notify the client object that the fetch has completed. The client can then call the `.entries()` method on the controller to get the sub-tree of entries for the TypeCreate object. The Sidebar has been slightly (!) refactored so that it's emphatic about what it does: it shows the brand, nav, and user sections of the sidebar. The styling has been moved to a separate file, the better to emphasize this. The SidebarItems file is where all the magic-- and a lot of ugly-- is hidden. The main purpose of the SidebarItems is to render the tree of entries passed to it. That's it. But it also has to be able to read the URL and highlight which entry is currently being shown by the router, and it has to be able to open up all the parent objects of the "current" link so that the user gets a clear sense of where they are navigationally. Most messy: the `reclick()` function intercepts clicks on anchors and, using the same logic as the router, decides if the router would *not* handle the navigation event. If the router would not, it takes on the responsibility for reaching into the currently visible table, modifying the filter and triggering a new `.fetch()`. Somewhere along the way I boyscoutted another `switch` statement or two into lookup expressions. --- <sup>1</sup> One of the reasons for this is that the Administrator Application's sidebar, routes, and command palette will all get their data from a single source of truth, and that single source will be independent of any of those. This is a step in that direction. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| authentik | ||
| blueprints | ||
| cmd | ||
| internal | ||
| lifecycle | ||
| locale | ||
| schemas | ||
| scripts | ||
| tests | ||
| web | ||
| website | ||
| .bumpversion.cfg | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| docker-compose.yml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| ldap.Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| manage.py | ||
| poetry.lock | ||
| proxy.Dockerfile | ||
| pyproject.toml | ||
| radius.Dockerfile | ||
| README.md | ||
| schema.yml | ||
| SECURITY.md | ||
What is authentik?
authentik is an open-source Identity Provider that emphasizes flexibility and versatility. It can be seamlessly integrated into existing environments to support new protocols. authentik is also a great solution for implementing sign-up, recovery, and other similar features in your application, saving you the hassle of dealing with them.
Installation
For small/test setups it is recommended to use Docker Compose; refer to the documentation.
For bigger setups, there is a Helm Chart here. This is documented here.
Screenshots
| Light | Dark |
|---|---|
 |
 |
 |
 |
Development
Security
See SECURITY.md
Adoption and Contributions
Your organization uses authentik? We'd love to add your logo to the readme and our website! Email us @ hello@goauthentik.io or open a GitHub Issue/PR! For more information on how to contribute to authentik, please refer to our CONTRIBUTING.md file.