If you are running the so called second database, I think using OAuth 2.0
is superfluous. If the second database is an outer to your system, and in
fact you communicate with that DB via an API (as you said), then you can
use OAuth 2.0. Also, it depends on the way the second DB checks a given
I agree that login_hint from Google OAuth2.0 API sounds appropriate.
On Friday, November 1, 2013 10:47:00 PM UTC+2, Hitoshi Uchida wrote:
Hi,
If you use Google OAuth2.0 API, how about using login_hint parameter to
identify the domain of user's email address ?
