Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3ADE1187F7 for ; Thu, 19 Nov 2015 11:35:11 +0000 (UTC) Received: (qmail 66284 invoked by uid 500); 19 Nov 2015 11:35:11 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 66242 invoked by uid 500); 19 Nov 2015 11:35:11 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 66215 invoked by uid 99); 19 Nov 2015 11:35:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2015 11:35:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id F0F1A2C1F5F for ; Thu, 19 Nov 2015 11:35:10 +0000 (UTC) Date: Thu, 19 Nov 2015 11:35:10 +0000 (UTC) From: "Sergey Beryozkin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FEDIZ-138) Improve IDP Login experience MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sergey Beryozkin created FEDIZ-138: -------------------------------------- Summary: Improve IDP Login experience Key: FEDIZ-138 URL: https://issues.apache.org/jira/browse/FEDIZ-138 Project: CXF-Fediz Issue Type: Improvement Components: IDP Reporter: Sergey Beryozkin Priority: Minor Proposal: The first step is to replace the default name/password Spring Security name/password dialog with a more user friendly page asking for the name and password with some Welcome IDP banner, the default dialog is of course can be replaced in the product - but it would be good to have something better even OOB. I'm assuming it would require customizing the authentication/MVC flow. The second step: at the moment, if no realm is provided by RP, IDP form is displayed, where a user is asked to select a home realm, and then the user is challenged with the authentication dialog, thus if a user is expected to authenticate into the current IDP then two screens/steps are involved. Thus it all should be combined into a single page. Example: a form would have name/password fields so that a user can authenticate immediately into the current realm and if partner IDPs are available then the form would also have buttons like "SignIn with IDP B", "SignIn with IDP C". I guess this is also customizable in the production but it would nice to have a composite page available OOB. IMHO this would be in line with the best login practices (such as those advocated by Google, etc, where a user is expected to press a minimum number of buttons during the login process) -- This message was sent by Atlassian JIRA (v6.3.4#6332)