[
https://issues.apache.org/jira/browse/OPENMEETINGS-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik resolved OPENMEETINGS-1971.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 4.0.7
Should be fixed
Please see unit test here:
https://github.com/apache/openmeetings/commit/4139f8a2fac18e5b204a439b608395aa8ff7202e#diff-56cc99364d50d3d1db46cf36ed9ff577R79
> Accept nested profile object in OAuth2
> --------------------------------------
>
> Key: OPENMEETINGS-1971
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1971
> Project: Openmeetings
> Issue Type: Improvement
> Components: OAuth
> Affects Versions: 4.0.6
> Reporter: Sadra Heidari
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 4.0.7
>
>
> Hi,
> In the OAuth2 config page there are inputs for defining user profile fields
> from OAuth server response:
> * Login param name
> * Email param name
> * Firstname param name
> * Lastname param name
> User can only write down field names from the *root* of the returned object,
> but if any of the fields is wrapped with a base object, it can not be used.
> Assume that the returned response is as follows:
> {
> "hasError": false,
> "result" : \{ "username": "test", "email": "a...@test.com"}
> }
> In this case user is unable to define the username field because it's put in
> an inner object.
> It will be useful if you can support nested objects so that the user can
> define "*result.username*" as Login param name.
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
