I took

hydra-login-consent-node

and created

hydra-headless-ts

My requirements lent me to trusting in a system like

hydra

, and writing the code that i either needed to proxy or rewrite.

/oauth2/auth

runs its own proxy and then sends to

hydra

which will handle the login and consent routes, and as currently implemented they are accepted with the basic validation and leans into using only Google's Consent, rather than showing what was in the consent forms. Everything in

hydra-login-consent-node

has been migrated into functional paradigms in this application. The histories, while present in the

fork

have digressed widely. If you see horrible over/under simplifications, or just straight up wrong...issues, please let me know. I set out to solve a problem, that i didn't know the underlying pattern of, other than a high level. I may have taken choices that are seen as...let's say...moronic. I'm a sarcastic person. https://github.com/jeffdyke/hydra-headless-ts/blob/main/OAUTH2_ARCHITECTURE.md