From cb84f5718604188f7aa5afd3451c10dd8f4cbce6 Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Wed, 9 May 2018 17:25:49 +0200 Subject: [PATCH] Implicit grant updated --- implicit.html | 135 +++++++++++--------------------------------------- infos.js | 4 +- 2 files changed, 30 insertions(+), 109 deletions(-) diff --git a/implicit.html b/implicit.html index 9fe6552..ee15f8d 100644 --- a/implicit.html +++ b/implicit.html @@ -18,53 +18,24 @@

State

The process should also return the state provided.

-        
-

Code

-

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

+
+

Access Token

+

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

+

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

For us, it is a JWT:

-

+            

             

Which once decoded is:

-

-            

Tokens

-

Now the client server need to retrieve an Access Token - and a Refresh Token by 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. - Unlike in this demo, that MUST be done server side.

-
- Get Access & Refresh Tokens from Code -
-

Response from /token

-

token endpoint URL: Nothing yet.

-
Nothing yet.
-

decoded access-token

-
Nothing yet.
-

decoded refresh-token

-
Nothing yet.
+

             

Using the API

+

API Call

+

API URL: Nothing yet.

Make an API call with the access token

API URL: Nothing yet.

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.