AgendaAndAudience

This is what we will be doing in the next 4 posts.

i will include this diagram more than once.

O-Auth2-Authorization Code Grant

The below series of posts is useful for,

  1. Micro-services Developers.
  2. Dev/Sys Specialists.

towards,

  1. How oAuth2 Grant Selection works by example.
  2. How Auth providers make things easy.

It is NOT,

  1. a guide book of oAuth2.
  2. about grant selection.

Some Pre-requisites before you jump in,

  1. Basic node js.
  2. Basic web development.
The first series of posts are about oAuth2, Let's get started.

Next-->

Comments

  1. Mahesh RajannanDecember 24, 2018 at 5:50 PM

    Post a simple node js the US election polling one.3:00 PM SAT

    Because i am starting on windows laptop. I might as well show how to install node js on windows.

    Show the keys but obviously regenerate it.

    What is the plan ? Remember the medium article on O-Auth and the 3 modes of authorization.

    First diagrammatically explain what is the mode of authorization , that we are currently going to do.

    Right next to the arrow overlay with pictures of UI and the tokens exchanged. or may be 2 pictures ...one with UI and other with tokens.

    Then add an other one with a brief statement of both pictures.

    When you are just entering a place, read. When you are bored then start browsing...shopping and so on. but...my mac is eating a corner of my head.

    3:41. Ok sounds like a plan.

    Gather references of the medium link for the diagram.

    Make the code work in windows.

    appbase.io is also a cool thing.The node elastic d3 is a cool thing.
    Logstash jenkins is a cool thing.Jenkins audit trail is a cool thing.already published the gradle ..
    mapbook with ES , open maps and leaflets...2 state machines make the program insanely complex.
    one on jqgrid...may be even make it a running app.beats is a cool thing.

    coverity comparison

    Time now11:30 gosh

    1. Run the code as is.
    2. Put screenshots.
    3. pull sources and draw diagram.
    4. Take anything you need from windows.

    ReplyDelete

Post a Comment

Popular posts from this blog

Debug The App With Chrome

Image
DEBUG THE APP. 1. Enable Chrome Developer Tools. 2. Click Login and see the login page. a. Check the developer tool configuration. 3. The federated login page. Note : The federated login page is injected by lock.min.js 4. Observe the Requests. Note :Observe the client id, it is the same as the Auth0 settings page. 5. On click Auth0Login. The call goes to Auth0 server and client id is passed. 6. Examine Authorize. Note : a. client id. b. response type param is code. c. redirect uri is http://localhost:3000/callback, as we initialized in our code Auth0 page. d. scope is email id, name and picture(Which is not available for me). e. realm username-password-authentication, the grant type basically. f. Explore request headers and response headers.  g. Headers are chosen, instead of other params, for security reasons. h. Note the set-cookie (http secure) under response header. i. The authorization code under response header(7pmf*****cbl) .
Read more

RunTheApp

Image
Run The App. Federated Auth(orization) Steps 1. Checkout code . 2. Create credentials in auth0. 3. Set the credentials in .env file 4. install (npm install). 5. Run (node app). Don't worry in the next page, i included some screenshots for help. References : https://auth0.com/blog/building-and-authenticating-nodejs-apps/ <--Previous   Next-->
Read more