Hi Lillian, thanks for helping.
The quoted post seems to be in the case where the endpoint was not a direct link to the file. It’s a bit different here, where we directly provide the file link.
Also, this seems to work in some cases:
Also, tooltip of oauth2 callback user info paths property says
Paths in the token response to other user properties. Supported properties are name, username, email, email_verified and avatar. Format is property:path, eg: name:params.info.name
If not by URL, how do we do it? Should I base64encode it in the file?
Edit: Let me try the 2-step process, where the image avatar result is in another query, instead of the token response, and I’ll post again.