We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, some providers do not reply with a flat JSON; for example, dataporten.no has a /userinfo endpoint where the user's details are stored under user:
/userinfo
user
HTTP/1.1 200 OK Content-Type: application/json; charset=utf-8 { "user": { "userid": "...", "userid_sec": ["feide:..."], "name": "...", "email": "...", "profilephoto": "p:..." }, "audience": "..." }
Source: https://docs.feide.no/developer_oauth/technical_details/oauth_authentication.html
The user_json function assumes a flat JSON instead:
user_json
ckanext-oauth2/ckanext/oauth2/oauth2.py
Lines 173 to 175 in e68dd26
I made a workaround for that, but it is not a generic fix: NINAnor@f86448f
The text was updated successfully, but these errors were encountered:
Any feedback on that?
Sorry, something went wrong.
No branches or pull requests
Hi,
some providers do not reply with a flat JSON; for example, dataporten.no has a
/userinfo
endpoint where the user's details are stored underuser
:Source: https://docs.feide.no/developer_oauth/technical_details/oauth_authentication.html
The
user_json
function assumes a flat JSON instead:ckanext-oauth2/ckanext/oauth2/oauth2.py
Lines 173 to 175 in e68dd26
I made a workaround for that, but it is not a generic fix: NINAnor@f86448f
The text was updated successfully, but these errors were encountered: