You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Sadra Heidari (JIRA)" <ji...@apache.org> on 2018/12/09 16:23:00 UTC

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

Sadra Heidari created OPENMEETINGS-1971:
-------------------------------------------

             Summary: 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


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)