Our developer experience squad is placing this as one of their priorities for this quarter but they need to review all the issues around the U&P plugin to see what is possible right now.
We have identified though that our future course of action with regards to U&P is we will be working in parallel on two things:
- Get U&P functionally stable in Strapi v4 so that it can continue to function with a reasonable degree of it’s intended purpose
- Start planning on building an entirely new end-user authentication plugin that will replace U&P (ideally one with field level permissions, but this isn’t confirmed).
Our problem is largely that to “fix” U&P to the level we want it, it would mean breaking changes which we can’t do while we are in the v4 development cycle and with no idea when we will start Strapi v5 development. So our only option right now is to either build ourselves a replacement plugin or possibly contract the development of such a plugin externally (largely due to our small team size, we can’t handle it ourselves right now).
I’ll have more information once the Product Managers review some of the U&P issues.