You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/30 10:28:27 UTC

[jira] [Commented] (SYNCOPE-701) New end-user UI

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

ASF GitHub Bot commented on SYNCOPE-701:
----------------------------------------

GitHub user andrea-patricelli opened a pull request:

    https://github.com/apache/syncope/pull/11

    SYNCOPE-701 first working implementation

    

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

    $ git pull https://github.com/andrea-patricelli/syncope SYNCOPE-701

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

    https://github.com/apache/syncope/pull/11.patch

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

    This closes #11
    
----
commit 223a64e26deff69a4ed8275d0f1348ca4e130a01
Author: Andrea Patricelli <an...@tirasa.net>
Date:   2015-10-05T13:12:55Z

    SYNCOPE-701 first working implementation

----


> New end-user UI
> ---------------
>
>                 Key: SYNCOPE-701
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-701
>             Project: Syncope
>          Issue Type: New Feature
>            Reporter: Francesco Chicchiriccò
>            Assignee: Andrea Patricelli
>             Fix For: 2.0.0
>
>
> Before SYNCOPE-156, the admin console used to offer self-service features like as self-registration, profile maintenance and password reset.
> The idea is to built a separate web application providing such features; some requirements:
>  # extremely customizable on deployment basis: not only look & feel, but also application logic (this sets one of glamour JS frameworks -as AngularJS - as candidate)
>  # keep admin UI attitude of being gateway for accessing REST services exposed by core: this might require to build a sort of 'proxy' application to be contacted by client-side JS code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)