I could really use some help making sense of the various options available to me for completely customizing the login form & having it appear within our app’s onboarding flow rather than being redirected to the Auth0 domain. We have a React-based single page app and we are currently using the classic universal login experience. We would like to have more control over the login form and be able to completely customize it & have it be part of our application’s codebase. Would that be an example of an embedded login? It sounds like there are some warnings in that doc around the increased security risks of going that route. How does embedded differ from using one of the various JS libraries (auth0-js, auth0-spa-js, auth0-react)? Or does the embedded approach use those libraries (e.g. they’re not different)?
In sum, if we want to completely host and manage the login form (allowing both social and email/password authentication) and use it without any redirects from within our SPA onboarding flow, what docs should I be looking at for guidance? I can’t seem to figure out which category/bucket of Auth0 docs this approach falls under. Also, can you please point to any examples of self-hosted SPA login form usage?
Thanks a bunch!