Changes for page 2. Authenticating with your OIDC client and fetch collab user info
Last modified by messines on 2021/06/08 17:32
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -43,7 +43,7 @@ 43 43 44 44 ==== Scope ==== 45 45 46 -In the request you can see a scope **parameter** 46 +In the request you can see a **scope** **parameter** 47 47 48 48 * **openid : **This scope is required in oidc, it contains basic information of the user such as it username, email and full name. 49 49 * **group **( optional ) **: **This scope is provided by our service, if you add it to your authorization code grant request, the futur access token generated will be able to read which units and groups the logged user belongs, it can be very important for your application. You can notice on the screenshot in the abstract section that **Consent required **is **on, **it means that at loggin time, the user will be asked if he allow your application to access there unit and group membership ... ... @@ -112,7 +112,7 @@ 112 112 /GET https:/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/userinfo 113 113 ))) 114 114 115 -and just provide the access token as **Auth entication** header115 +and just provide the access token as **Authorization** header 116 116 117 117 [[image:Screenshot 2020-07-15 at 18.28.28.png||height="161" width="566"]] 118 118