56
This is common with federated identity systems where a service authenticates users from many identity providers.
Your email address is used to look up which identity provider can authenticate you. This could be a work, school, or personal account. Upon entering your work email, you would be redirected to a URL from your workplace where you enter your ...
32
The purpose of this is to redirect to the account's identity provider. However the use case is not selecting between personal login providers such as Facebook or Google. It's to support organisational logins which have organisation-specific user identifiers.
Personal login flows are selected with a dedicated button. The first image in the docs has a "...
4
I think this is used for when some logins may be forwarded to a seperate auth service. in this case you don't want to see the password at all.
eg, say you allow the user to login to your site with google/facebook/email you can detect which one they want to use from the identifier, but you dont want to see their google password
https://auth0.com/docs/...
3
There might be more than one way to authenticate yourself to a service, especially at their scale.
For example, Google lets you use your phone instead of a password, so that means that they'll want to show that screen instead of a password prompt. Microsoft do too, and also provide options for using physical hardware keys like smart cards, fingerprint ...
3
I'm sure there'll be more but I'll point to three concerning points that I find especially relevant.
Scalability
Long story short, a wild west DB access strategy scales very bad. Economically can be unaffordable as the system grows in popularity. The more concurrency the more resources you need for each DB. To my experience, scaling out/up middlewares (or ...
2
Be aware that allowing direct has multiple impacts.
From a security perspective you present the database to the "public" (whatever public is in your context). With an application server inbetween you can apply much stricter network configurations.
But my main concern would be a different one. When your users connect directly to the database, ...
2
is there any benefit of choosing one over the other ?
Technically - no. As you mentioned, for humans it is much easier to remember username and password. A client application can store a huge public key and use it...
What are the techniques used for the same purpose when two
machines/programs are communicating ?
There are several techniques. A commons one ...
Only top voted, non community-wiki answers of a minimum length are eligible
