In the legacy lock deprecation announcement, , it sounds as if a custom domain is highly recommended (but not required) when using embedded login. Is this indeed the case? If we keep using embedded logins with lock version 11, will things work, subject to the hazards of cross-origin issues? Or is …

Disabling Legacy Lock API with embedded login and no custom domain

Topic		Replies	Views
Change of behavior to non-deprecated API with Legacy Lock API deprecation Get Help legacy-deprecation , cors	1	4165	July 29, 2019
Embedded with custom domain vs Universal login Get Help auth0 , security , embedded-login , universal-login	4	4488	June 19, 2019
Embedded login/lock not working Get Help login-experience , login-prompt-new-experience	4	1000	July 14, 2023
Embedded Lock SKD redirection Get Help login-experience , login-prompt-new-experience	0	707	July 10, 2023
Embedded login users authentication issue on safari Get Help lock , auth0	2	3265	May 11, 2020