If you're building an API which needs a high-security level, it can be very useful to use a 2FA. We could pretty easily support two-factor authentication using the current implementation of the Users & Permissions plugin. For more details, please see https://github.com/strapi/strapi/issues/786

Currently, we don't offer the capability to add validations constraints on a field to avoid to contribute unintended data from the administration or the API.

The current implementation only supports one provider by user. This feature will allow your user to support multiple authentication providers like Google and Twitter for the same user. Related issue: https://github.com/strapi/strapi/issues/2468

As a Project Owner, TeamLead, Strapi Admin etc, id love to see who did what and when. Id love to see an edit history for a content item, to potentially discover issues later one, or be able to trace unwanted content changes. Secondly, this audit log would be neseccary when delivering content for specific industries, such as in car software. Those changes need to be traceable and archived for 10 Years, by German law. see: https://github.com/strapi/strapi/issues/11500

I would like to be able to set password complexity. It would be convenient to set restrictions to password length, big letters, small letters, numbers, etc see: https://github.com/strapi/strapi/issues/4990

Part of the SSO, we would like to support permissions management via third parties such as Active Directory, LDAP, JumpCloud, etc. It includes fields synchronization and roles mapping.

Currently, the plugin which allows you to manage users and permissions doesn't support a provider system like it's already the case with the email plugin For more details, please see https://github.com/strapi/strapi/issues/1819

Currently, you cannot change the user email because it works like a unique ID. As we allow to edit the user password, we should also offer the ability to edit the email. This is the purpose of this feature. More details in this issue: https://github.com/strapi/strapi/issues/2691

When integrating with oauth2, I think it's more common to use strapi as resource server instead of client(strapi is headless). It's the duty of frontend (like nextjs) to get user authenticated and obtain the access token which used in Authentication header when access strapi, what strapi should do is validate access token and get user info from it. This make strapi more easy to integrate with other backend. see: https://github.com/strapi/strapi/issues/12207