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

Andrea Patricelli commented on SYNCOPE-1018:
--------------------------------------------

Hi Govinda,

Nice to meet you and glad to hear that you want to contribute :)
Currently we haven't a social login mechanism in Enduser, though I think that 
the issue is a bit different. The goal of the issue is to provide a feature 
that allows social registration, that is the possibility to register (create an 
account) on Syncope through social network, taking some (basic) information 
directly from the social network and filling some fields (if present). The most 
common examples of interesting fields could be the mail or the firstname, etc.
A further improvement could also be social-login to the self update section of 
the enduser, but this requires to work also on core module, the community is 
currently discussing about this and I do not exclude that something could be 
developed in the next months.
BTW I suggest you to start reading the reference guide at [1] to better 
understand what Enduser is and what is the aim of this module.

Best regards,
Andrea

[1] https://syncope.apache.org/docs/reference-guide.html#enduser-application

> 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, 
> 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+, ...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to