From dev-return-15604-archive-asf-public=cust-asf.ponee.io@syncope.apache.org Thu May 3 16:59:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8F6AE180625 for ; Thu, 3 May 2018 16:59:05 +0200 (CEST) Received: (qmail 83671 invoked by uid 500); 3 May 2018 14:59:04 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 83660 invoked by uid 99); 3 May 2018 14:59:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2018 14:59:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1FFEBC05EE for ; Thu, 3 May 2018 14:59:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id SglcqCJrZwpC for ; Thu, 3 May 2018 14:59:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id ED41F5FC6F for ; Thu, 3 May 2018 14:59:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 2A120E12CF for ; Thu, 3 May 2018 14:59:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 91F81212A1 for ; Thu, 3 May 2018 14:59:00 +0000 (UTC) Date: Thu, 3 May 2018 14:59:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: dev@syncope.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SYNCOPE-1270) OpenID Connect client feature MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SYNCOPE-1270?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 462556#comment-16462556 ]=20 ASF subversion and git services commented on SYNCOPE-1270: ---------------------------------------------------------- Commit 797fd1cbd801aedabb54b5d1dcb65d34636adec5 in syncope's branch refs/he= ads/master from [~dimaayash] [ https://git-wip-us.apache.org/repos/asf?p=3Dsyncope.git;h=3D797fd1c ] [SYNCOPE-1270] implementation for OpenID Connect for Admin Console and Endu= ser - This closes #74 > OpenID Connect client feature > ----------------------------- > > Key: SYNCOPE-1270 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1270 > Project: Syncope > Issue Type: New Feature > Components: extensions > Reporter: Dima Ayash > Assignee: Francesco Chicchiricc=C3=B2 > Priority: Major > Fix For: 2.0.9, 2.1.0 > > > This feature implements an SSO access to the Enduser UI and Admin Console= by using [OpenID Connect 1.0|http://openid.net/connect/] which is a simple= identity layer on top of the OAuth 2.0 protocol. It allows Clients to veri= fy the identity of the End-User based on the authentication performed by an= Authorization Server, as well as to obtain basic profile information about= the End-User in an interoperable and REST-like manner. > The flow for this feature will be possibly as follow (using Google as an = example of OpenID Connect Provider): > # From Enduser or Admin login UI, the user can choose to be authenticated= using Google account. > # Check if the user has a valid session, otherwise prompts the user to l= ogin by redirecting him to the Google Login UI. > # After the user login successfully to his Google account, grant him an = access to Enduser UI or Admin console. > This will be achieved by following the OpenId Connect required flow, leve= raging possibly from CXF features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)