AuthFlow is a simple login system for websites that uses Google’s oAuth Plataform
It works this way:
- You call AuthFlow’s API that redirects your user to a login page
- The user logs in with AuthFlow and AuthFlow handles the result
- We redirect users to a special page that adds a cookie
- You call that cookie when needed
What you get when you add the cookie isn’t just a JSON, it’s a JSON Web Token, that you can decrypt and validate on the server or client side.
Check it out here:
What’s your opinion?
- Seems cool
- Bad Idea
Thanks for reading!
App name or redirect URL contains words in our profanity filter
from a quick skim of the project, is there any reason why there’s an overhead of running every URL through a profanity filter? I can’t see why that’s even needed.
Hi @Un-index! I thought it may be useful because that information (app name, redirect URL) is public and is not related to the project.
It’s better to run a profanity filter always so we don’t have anyone blaming AuthFlow for that
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.