This repository was archived by the owner on Apr 26, 2024. It is now read-only.
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
OIDC/OAuth client and Nextcloud backend #8511
Description
Description:
When using Nextcloud as an external identity provider, its JSON response from the userinfo endpoint is as follows:
{
"ocs":{
"meta":{
"status":"ok",
"statuscode":200,
"message":"OK"
},
"data":{
"enabled":true,
"storageLocation":"\\/var\\/www\\/nextcloud\\/data\\/edg@privacyinternational.org",
"id":"edg@privacyinternational.org",
"lastLogin":1602147919000,
"backend":"Database",
"subadmin":[],
"quota":{"free":78983929856,"used":17659078,"total":79001588934,"relative":0.02,"quota":-3},
"email":null,
"phone":"",
"address":"",
"website":"",
"twitter":"",
"groups":["admin"],
"language":"en",
"locale":"",
"backendCapabilities":{"setDisplayName":true,"setPassword":true},
"display-name":"edg@privacyinternational.org"
}
}
}
Which obviously isn't mapped properly.
I've manually hacked the OIDC mapping provider so it brings in the id, but it'd be great if someone who knew what they were doing on the Synapse side could make this connection work properly!