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

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

Github user ilgrosso commented on a diff in the pull request:

    https://github.com/apache/syncope/pull/13#discussion_r61735681
  
    --- Diff: 
client/enduser/src/main/java/org/apache/syncope/client/enduser/SyncopeEnduserApplication.java
 ---
    @@ -154,6 +155,16 @@ public IResource getResource() {
                     return new LogoutResource();
                 }
             });
    +        
    +        mountResource("/api/self/islogged", new 
ResourceReference("userAuthentication") {
    +
    +            private static final long serialVersionUID = 
-128426276529456602L;
    +
    +            @Override
    +            public IResource getResource() {
    +                return new UserAuthentication();
    --- End diff --
    
    Please rename `UserAuthentication` according to its mount point.


> Once authenticated to enduser, "Cancel" brings nowhere 
> -------------------------------------------------------
>
>                 Key: SYNCOPE-798
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-798
>             Project: Syncope
>          Issue Type: Bug
>          Components: enduser
>    Affects Versions: 2.0.0-M2
>            Reporter: Francesco Chicchiriccò
>            Assignee: Matteo Di Carlo
>             Fix For: 2.0.0
>
>         Attachments: pointless page.png
>
>
> How to reproduce:
>  # log into enduser
>  # hit the red button Cancel on the bottom
>  # you are redirected to an empty page (see screenshot attached)
> Cancel should be equivalent to Logout (so it is really needed? The logout 
> button is already there).
> Incidentally, the same pointless page is returned when accessing 
> /syncope-enduser if authenticated - which looks wrong, the excepted landing 
> page should be first one, e.g. "crendentials".



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

Reply via email to