syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SYNCOPE-1018) Social registration for Enduser UI
Date Fri, 11 May 2018 12:40:00 GMT


ASF GitHub Bot commented on SYNCOPE-1018:

GitHub user DimaAy opened a pull request:

    [SYNCOPE-1018] self registration for OpenID Connect


You can merge this pull request into a Git repository by running:

    $ git pull 2_0_X

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #76
commit e7d679512650e091a01fba19374f2149b8b19439
Author: dayash <dima.ayash@...>
Date:   2018-05-11T10:28:52Z

    [SYNCOPE-1018] self registration for OpenID Connect


> Social registration for Enduser UI
> ----------------------------------
>                 Key: SYNCOPE-1018
>                 URL:
>             Project: Syncope
>          Issue Type: New Feature
>          Components: enduser
>            Reporter: Francesco Chicchiriccò
>            Priority: Major
>              Labels: gsoc2017
>             Fix For: 2.0.9, 2.1.0
> Provide an optional feature, to exploit for self-registration via [Enduser UI|],
which allows to take the initial values for some attributes in Syncope from a profile owned
by the registering user in one of most popular social networks as Twitter, LinkedIn, Facebook,
Google+, ...
> The main goal is to provide the ability to create an user on Syncope by self-registering
through the Enduser  UI. 
> Attributes "mapped" to the source social network should be defined in a mapping specified
through the [Admin Console|].
> Common examples of interesting fields could be the mail or the firstname, etc.
> Moreover the administrator should have the ability (through the Admin UI) to add an n-th
[OAUTH2|] provider and enable it as self-registration source; so the development
should be "open" and must not be focused only on a finite number of social networks. 
> Work requires also a bit of development on [Core module|].

> A further improvement could also be social-login to the self update section of the enduser,
the community is currently discussing about this.

This message was sent by Atlassian JIRA

View raw message