> 1. The user clicks Login within the application.
> 2. Your Auth0 Authorization Server redirects the user to the login and authorization prompt.
> 3. The user authenticates using one of the configured login options and may see a consent page listing the permissions Auth0 will give to the application.
Here's the problem as I see it: say I'm Acme inc. and I create an app that does this. The user logs in, sees "allow Acme to access your account", clicks OK, my app gets access token, all good.
The problem is if a black hat does the exact same thing, with the authorization server and all, directs user to an interface that shows the exact same (and actually legit) "allow Acme to access your account" screen, except their code grabs the access token in the end.
I'm not 100% sure how the flow suggested by auth0 is helpful in addressing this compared the flow where the client secret is just stored in the app (and is not actually a secret anymore). The secret is what can prove to OAuth server the identity of the client. If there's no secret it's impossible: the server can't know if that's actually a client I wrote or a client written by malicious attacker to mimic my client but to steal user's tokens, right?
I guess I don't get something fundamental or it's not a problem that can be solved at all (not this way).