From 64adb9eb672e108b3f0567a8ee9ec126193c4457 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Michaud?= Date: Fri, 18 Feb 2022 12:35:22 +0100 Subject: [PATCH] docs: update roadmap with new priorities based on feedbacks (#2878) --- docs/roadmap.md | 29 ++++++++++++++++++----------- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 5bf4c8871..91cbc46d0 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -14,8 +14,11 @@ ideas and plans with you. Below are the prioritised roadmap items: -1. **[In Preview](./configuration/identity-providers/oidc.md)** *this roadmap item is in preview status, more - information can be found in the docs*. +1. Webauthn needs to be implemented because U2F is being deprecated in the browsers. Chrome displays an annoying popup +advertising the deprecation. This is being implemented [here](https://github.com/authelia/authelia/pull/2707). + +2. **[In Preview](./configuration/identity-providers/oidc.md)** *this roadmap item is in preview status since information + is not yet persisted in the database. More information can be found in the docs*. [Authelia acts as an OpenID Connect Provider](https://github.com/authelia/authelia/issues/189). This is a high priority because currently the only way to pass authentication information back to the protected app is through the use of HTTP headers as described @@ -23,17 +26,21 @@ use of HTTP headers as described however, many apps either do not support this method or are starting to move away from this in favour of OpenID Connect or OAuth2 internally or via plugins. -2. [Administration interface](https://github.com/authelia/authelia/issues/974). This is useful in many cases to -properly manage users and administrate activities like unbanning banned users. In the future we can even think of -adding/removing users from there, request a password reset for a user or all users, request a 2FA enrollment, -temporarily block users, etc... +3. [Multilingual full support](https://github.com/authelia/authelia/issues/625). Support as been added but we heed to study multiple providers like Crowdin or Weblate +to help us translate in more languages and make Authelia available to even more people around the world! -3. [User interface](https://github.com/authelia/authelia/issues/303). This will help the users manage their 2FA -devices, reset their password, review their authentication activity. -In the future we envisage users will be able to customize their profile with an avatar, set their preferences -regarding 2FA and according to the global policy defined by administrators, etc... +4. [Protection of multiple root domains](https://github.com/authelia/authelia/issues/1198). This request has been upvoted many times and we heard you! +Currently, an Authelia setup is only able to protect all subdomains of a given root domain. This situation is challenging for +administrators maintaining services across multiple root domains so we have decided to prioritize this to enable those deployments. -4. [Facilitate setup on Kubernetes](https://github.com/authelia/authelia/issues/575). There are mainly two objectives +5. [User/Administrator interface](https://github.com/authelia/authelia/issues/303). Many use cases raised on Github relates to +being able to audit, configure and administrate a given account on Authelia. For instance, a user should be able to reset the password +manage MFA hardware devices and personal security policies, etc... An administrator should be able to unban accounts after a regulation ban, +kill sessions to reduce security risk due to compromised accounts and many other things. This item will be decomposed into multiple +items for implementing the features but there is preparatory work to be done on the permissions (likely role-based) we want to +implement. + +7. [Facilitate setup on Kubernetes](https://github.com/authelia/authelia/issues/575). There are mainly two objectives here. First, we need to provide the documentation required to setup Authelia on Kubernetes. Even though, some users already have it working and the feature is even tested in the project, there is a clear lack of documentation. The second item is to provide a Helm chart to streamline the setup on Kubernetes.