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
-
... ... @@ -44,10 +44,6 @@ 44 44 * **openid: **This scope is required because we use the OIDC protocol. It will give your app access to the user's basic information such as username, email and full name. 45 45 * **group **(optional)**: **If you request this scope, the future access token generated will authorize your app to identify which units and groups the user belongs to. 46 46 * **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. 47 -* **clb.wiki.read **(optional): access to GET Collab API 48 -* **clb.wiki.write** (optional): access to DELETE/PUT/POST Collab API 49 -* **clb.drive:read **(optional): access to GET Drive API 50 -* **clb.drive:write** (optional): access to DELETE/PUT/POST Drive API 51 51 52 52 {{info}} 53 53 The group and team scopes are a simple way for your app to grant permissions to its services and resources when you want to grant access to a very few units, groups, or collab teams. For more complex permission management, contact support. ... ... @@ -71,7 +71,7 @@ 71 71 72 72 ==== Request ==== 73 73 74 -/POST: [[https: ~~/~~/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/token>>https://iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/token]]70 +/POST: [[https:/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/token>>url:https:/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/token]] 75 75 76 76 with the following parameters: 77 77 ... ... @@ -113,7 +113,7 @@ 113 113 114 114 ==== Request ==== 115 115 116 -/GET: [[https: ~~/~~/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/userinfo>>https://iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/userinfo]]112 +/GET: [[https:/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/userinfo>>url:https:/iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/userinfo]] 117 117 118 118 with the following parameters: 119 119 ... ... @@ -125,7 +125,7 @@ 125 125 126 126 ==== Response ==== 127 127 128 -As response your app receives a JSON with all the information aboutthe logged user124 +As response your app receives a JSON with all the information on the logged user 129 129 130 130 (% class="box" %) 131 131 ((( ... ... @@ -148,7 +148,7 @@ 148 148 ], 149 149 "group": [ 150 150 "**group**-collaboratory-developers", 151 - "**unit**-all-projects-hbp-consortium-sga2-sp05- **administrator**"147 + "**unit**-all-projects-hbp-consortium-sga2-sp05-administrator" 152 152 ] 153 153 }, 154 154 "mitreid-sub": "30...62" ... ... @@ -155,10 +155,12 @@ 155 155 } 156 156 ))) 157 157 158 -The u nitfield above lists CollaboratoryUnitswhichthe user isamemberof,with the unitslashes instead of the colons you see in the Collaboratory UI.154 +The group field above lists Collaboratory Groups in the form "group-//groupname//" and Collaboratory Units in the form "unit-//unitname//" with the unitname using dashes instead of the colons you see in the Collaboratory UI. 159 159 160 - jupyterhubandxwikiareOIDC clientswith more advancedpermissionmanagement.156 +The team field above lists Collaboratory Teams in the form "collab-//collabname//-//role//" where //role //is one of admin, editor, or viewer according to the user's role in collab //collabname//. 161 161 162 - Theteam field above lists Collaboratory Teams which theuser is a memberof, in the form "collab-//collabname//-//role//"where //role //is one of admin,editor, or vieweraccording to theuser'srole incollab //collabname//.158 +jupyterhub and xwiki are OIDC clients. 163 163 164 -The group field above lists Collaboratory Groups which the user is a member of, in the form "group-//groupname//". It also lists Collaboratory Units which the user is an admin of, in the form "unit-//unitname//-administrator" with //unitname //using dashes instead of the colons you see in the Collaboratory UI. 160 +The unit field above lists is the list of unit the user is member of. The `unit-` prefix bellow the group field are the administration right for this user for the given unit, administration of unit is a separate concept than the unit themself. 161 + 162 +