Conversation
This reverts commit 46ae282.
src/Umbraco.Web.UI.Login/src/components/external-login-provider.element.ts
Show resolved
Hide resolved
…gin-screen # Conflicts: # src/Umbraco.Web.UI.Client/package-lock.json # src/Umbraco.Web.UI.Client/package.json
|
@iOvergaard not specific related to this, but I wonder if the installer should remove or should it wait for the new backoffice? |
Hi @bjarnef, the installer will follow Bellissima. The new installer, that we already built for Bellissima, works only with the management API and would be too cumbersome to backport to V13 as well. We suspect the impact is much larger for the login screen over the installer, since you will ever only see the installer as a developer. |
Prerequisites
Description
Move the login screen built for Bellissima into v13 to replace the existing one.
Breaking changes
/umbraco/loginby default) which is served throughlogin/index.cshtmlBackofficeControllerwill now redirect to the URL of the new login screen when not authorizedUmbLoginDirectivewill still be shown, but it has been rewritten and slimmed down to show the new login screen, which is a self-encapsulated custom element called<umb-auth />.Other changes
<umb-localize />is available to use, which mirrors the API of the existing Angular<localize />directive. This element can be used in its place and is necessary if building custom views for the login screen.Motivation
We want to remove legacy JavaScript tech from the most public-facing side of the backoffice: the login screen. The new login screen is built with Lit & TypeScript (tech from Bellissima) and will thus remove
angularandjqueryfrom the browser at least when you access the login screen.Screenshots