SAML, single sign on, 2FA confirmation, etc.
For example, I don't know what login method a user would be using (our own password? or redirect them to their corporate's auth portal) until they enter their email.
For example, I don't know what login method a user would be using (our own password? or redirect them to their corporate's auth portal) until they enter their email.
Basically a single page request (that then immediately fetches all the associated JaveScript and CSS) to run the entire app.
It is popular now because its a very small step from that to having a PWA (progressive Web application) which is progressive in the sense that it can be completely cached on the users device, and work with no connection to the Internet.
It also improves page-load performance in connected situations by there being no pages to load (after the first one).
While a solid approach, SPAs can suffer from long initial load times, as well as a tendancy to suffer from complexity that comes with any monolithic large app.
Log in with Corp acme. Log in with palantir. Log in with Facebook (Corp). Log in with Facebook (end user)... Etc.
You'd have to iterate through every customer with SAML / OIDC set up.
Even if you are just using end user, it's sometimes confusing if there are 10+ options because you have to remember... Ok not only do I gotta remember my email I used, how did I originally sign up? .. was it with Google? With Facebook... No wait did I use email and password...
But it also happens plenty of places where single sign in isn't an option. Like the biggest two supermarkets Tesco.com and Sainsburys.co.uk here in the UK.