Skip to content

Instantly share code, notes, and snippets.

@unixsuperhero
Last active August 6, 2017 21:48
Show Gist options
  • Save unixsuperhero/cd5e43c4df0c142164277be3ae9086d2 to your computer and use it in GitHub Desktop.
Save unixsuperhero/cd5e43c4df0c142164277be3ae9086d2 to your computer and use it in GitHub Desktop.
edukate info

NOTE: We can probably skip a step!

If the user is clicking "Get Started!" then why would they have to come back to our page?

Clicking it can send them to an endpoint in our app, that will do all the oauth registering and token generating. Then, that endpoint can redirect to Edukate and we can send that info to Edukate along with all the token/user info.


User Flow

  • User goes to our edukate financial page
    • clicks "Get Started!"
    • clicking "Get Started!" takes the user to an "Edukate" page

Our (Introductory) Edukate Page

User Flow (cont'd)

  • Edukate sends them back to our site to get authorized with our OAuth provider

    • The page that they land on will look like 1 out of possibly 2 different pages
      1. If the user is already logged into our site it will say:
      • "Do you want to add Edukate for your THEACCTNAME account?"
      1. If the user is not logged into our site it will:
      • Give them username/password fields to login with and grant access to Edukate
  • Once the user verifies that they want to grant access, we will redirect the user back to the edukate site, sending Edukate access tokens for the current user, etc.

  • Over time Edukate will send us information about the user?

  • Then, when the user goes to our Edukate Financial page...they will see a different page will all sorts of different stats and scores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment