syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Patricelli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SYNCOPE-1018) Social registration for Enduser UI
Date Thu, 02 Mar 2017 08:55:45 GMT

     [ https://issues.apache.org/jira/browse/SYNCOPE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrea Patricelli updated SYNCOPE-1018:
---------------------------------------
    Description: 
Provide an optional feature, to exploit for self-registration via [Enduser UI|https://syncope.apache.org/docs/reference-guide.html#enduser-application],
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|https://syncope.apache.org/docs/reference-guide.html#admin-console-component].
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|https://oauth.net/2/]
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|https://syncope.apache.org/docs/reference-guide.html#core].


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

  was:
Provide an optional feature, to exploit for self-registration via [Enduser UI|https://syncope.apache.org/docs/reference-guide.html#enduser-application],
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|https://syncope.apache.org/docs/reference-guide.html#admin-console-component].
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 social
network 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|https://syncope.apache.org/docs/reference-guide.html#core].


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


> Social registration for Enduser UI
> ----------------------------------
>
>                 Key: SYNCOPE-1018
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1018
>             Project: Syncope
>          Issue Type: New Feature
>          Components: enduser
>            Reporter: Francesco Chicchiriccò
>              Labels: gsoc2017
>             Fix For: 2.1.0
>
>
> Provide an optional feature, to exploit for self-registration via [Enduser UI|https://syncope.apache.org/docs/reference-guide.html#enduser-application],
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|https://syncope.apache.org/docs/reference-guide.html#admin-console-component].
> 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|https://oauth.net/2/] 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|https://syncope.apache.org/docs/reference-guide.html#core].

> 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
(v6.3.15#6346)

Mime
View raw message