[jira] [Commented] (OPENMEETINGS-1971) Accept nested profile object in OAuth2

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718579#comment-16718579 ] 

ASF subversion and git services commented on OPENMEETINGS-1971:
---------------------------------------------------------------

Commit f8516c33357883ef04d83d1c639760185ffb319d in openmeetings's branch refs/heads/master from [~solomax]
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=f8516c3 ]

[OPENMEETINGS-1971] second-level object is being found as expected


> 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
>
> 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": "aaa@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)