From f930fe33ce0d922ba8255b31b133046e8babde65 Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Tue, 13 Feb 2018 17:56:05 +0100 Subject: [PATCH] better interaction for demos --- brutalist.css | 3 +- login.html | 128 ++++++++++++++++++++++++++++++++++++++------------ 2 files changed, 100 insertions(+), 31 deletions(-) diff --git a/brutalist.css b/brutalist.css index e7c7599..f2ac238 100644 --- a/brutalist.css +++ b/brutalist.css @@ -35,8 +35,7 @@ code,pre { pre { padding: 1em; border: solid 2px; - font-size: 0.7em; - box-shadow: 8px 8px 0; } + font-size: 0.7em;} .button { display: inline-block; diff --git a/login.html b/login.html index 732867b..aa00e91 100644 --- a/login.html +++ b/login.html @@ -29,38 +29,108 @@

Yolo App login page

Authorization process done!

← go back to main page -

Tokens

-
Retrive tokens...
-

Decoded Code:

-
-

decoded from the code:

+

Code

+

The code is generated by the Authentication server and send back + to the client via the resource's owner user-agent

+

For us, it is a JWT:

+

Which once decoded is:

+
+

Tokens

+

Now the server need to retrieve an access-token and a refresh-token + using that code.

+

To achieve that the client will make a call to /token + using a basic auth creds

+

You have about 10 mins to retrieve them

+
+ Get Access & Refresh Tokens from Code +
+

Response from /token

+
Nothing yet.
+

decoded access-token

+
Nothing yet.
+

decoded refresh-token

+
Nothing yet.
+

Getting new access token without user interaction

+

The access tokens are the only tokens which are able to talk to the + Visibility API.

+

Access tokens live a short time (about 10 min to 1 hour)

+

This is why the client must require a new access token using its + refresh token. + That is just making another call to /token + But with different parameters. +

+ Get Access Tokens from Refresh Token +
+
Nothing yet.
+
Nothing yet.