Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5B03F200CB5 for ; Wed, 12 Jul 2017 17:51:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 59821169C39; Wed, 12 Jul 2017 15:51:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C53D3169C28 for ; Wed, 12 Jul 2017 17:51:07 +0200 (CEST) Received: (qmail 31215 invoked by uid 500); 12 Jul 2017 15:51:07 -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 31204 invoked by uid 99); 12 Jul 2017 15:51:07 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jul 2017 15:51:07 +0000 Received: from [192.168.0.3] (93-56-25-79.ip287.fastwebnet.it [93.56.25.79]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D01541A0029 for ; Wed, 12 Jul 2017 15:51:04 +0000 (UTC) Subject: Re: Access Tokens label in dashboard panel To: dev@syncope.apache.org References: <446190481.5850.1499802806106.JavaMail.zimbra@tirasa.net> From: =?UTF-8?Q?Francesco_Chicchiricc=c3=b2?= Message-ID: Date: Wed, 12 Jul 2017 17:51:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US archived-at: Wed, 12 Jul 2017 15:51:08 -0000 Hi , I am not completely sure that "Access Token" is actually misleading - wikipedia does not even mention OAuth about it: https://en.wikipedia.org/wiki/Access_token Anyway, if you think so we can change that label; only, I don't think that anything about "session" should be used, as JWT are not sessions. Other proposals? Regards. On 12/07/2017 17:19, Colm O hEigeartaigh wrote: > Yeah makes sense. > > Colm. > > On Tue, Jul 11, 2017 at 8:53 PM, Massimiliano Perrone wrote: > >> Hi guys, >> >> the dashboard page has four tabs. As you know one of this is called Access >> Tokens... >> >> Maybe we should change that name because access token is the standard name >> of an OAuth token so it's misleading. Maybe we can use something like >> sessions or authenticated sessions or authenticated users... >> >> WDYT? >> >> Best regards, >> >> Massi -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/