Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -48,7 +48,9 @@
48	48	* **team **(optional)**: **This scope is like the group scope lets your app identify the permissions of the user, but by identifying what collabs the user has access to and with what roles.
49	49	* **clb.wiki.read **(optional): access to GET Collab API
50	50	* **clb.wiki.write** (optional): access to DELETE/PUT/POST Collab API
51		-* **collab.drive **(optional): access to GET/POST/PUT/DELETE drive API
	51	+* **clb.drive:read **(optional): access to GET Drive API
	52	+* **clb.drive:write** (optional): access to DELETE/PUT/POST Drive API
	53	+* **collab.drive **(optional): former scope, should be use if clb.drive is not enought
52	52	* **offline_access **(optional)**: **provide refresh token
53	53
54	54	{{info}}
...	...	@@ -69,7 +69,7 @@
69	69	=== Access Token Request ===
70	70
71	71	(% class="wikigeneratedid" id="HRequest-1" %)
72		-Now that your app has the **authorization** **code** for a user, it can fetch the user ID Token and Access Token
	74	+Now that your app has the **authorization** **code** for a user, it can fetch the user access token
73	73
74	74	==== Request ====
75	75
...	...	@@ -107,7 +107,7 @@
107	107	}
108	108	)))
109	109
110		-Your app gets a response containing the **access token**, the **refresh token,** the **id token **and other information. The ID Token should be use by developer on their backend to read user informations such as username, first name, last name etc. The ID Token should be use internally, into your app only, the app which triggered the authentication. The access token will be use to reach APIs, the access token can be see as a card to access an ATM. ID Token is for Authentication, Access token is for Authorization. Refresh token is to re-ask a valid access token after expiration.
	112	+Your app gets a response containing the **access token** and other information.
111	111
112	112	== Access user info ==
113	113