
From nobody Sun Sep  4 15:35:19 2016
Return-Path: <wibrown@redhat.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91DD12B097 for <ldapext@ietfa.amsl.com>; Sun,  4 Sep 2016 15:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.41
X-Spam-Level: 
X-Spam-Status: No, score=-8.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwwVhxRqtIms for <ldapext@ietfa.amsl.com>; Sun,  4 Sep 2016 15:35:15 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E54F412B012 for <ldapext@ietf.org>; Sun,  4 Sep 2016 15:35:15 -0700 (PDT)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9A79485541 for <ldapext@ietf.org>; Sun,  4 Sep 2016 22:35:15 +0000 (UTC)
Received: from rei.prd.blackhats.net.au (ovpn-116-25.phx2.redhat.com [10.3.116.25]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u84MZDSg020865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ldapext@ietf.org>; Sun, 4 Sep 2016 18:35:14 -0400
Message-ID: <1473028512.26123.43.camel@redhat.com>
From: William Brown <wibrown@redhat.com>
To: ldapext@ietf.org
Date: Mon, 05 Sep 2016 08:35:12 +1000
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-vjn5HOtiE3GgsWHwUElE"
Mime-Version: 1.0
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Sun, 04 Sep 2016 22:35:15 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/joilzEekqk03M4-PZOnhe2xz9dg>
Subject: [ldapext] Request for feedback: draft-wibrown-ldapssotoken
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Sep 2016 22:35:17 -0000

--=-vjn5HOtiE3GgsWHwUElE
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I would like to ask for feedback on the submission
draft-wibrown-ldapssotoken [0]. Section 5 deals with the ldap components
of the implementation.

Thank you for your time and advice,

[0] https://datatracker.ietf.org/doc/draft-wibrown-ldapssotoken/

--=20
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane

--=-vjn5HOtiE3GgsWHwUElE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABAgAGBQJXzKGgAAoJEISUiynM+PAgLigQAInn5dt/7fIKe95XpH30U1a1
yLyMYqMKHXhx2ocKgVA4ikXLNJ2aXAr9gePaAu4N0TVRUHulp2Zl9OI6VMDdAcyP
uh3PdvxFuk3lPhq9yaAYEQ9ymlfh00DvAfxUuOWN60rWen8Cl5EPziOEvY1j4k03
/bQ3UR4IDDv50i7tc3pvj80fFHUZ+qDxd3qtEHEmXKQ23BBNP00p37/ixEbic+/F
y0CKi2H0FwN32BthvsM2g5/KSSwC87OWVqGMpA1Ee65GdRar86/g/uEKJIR54RD4
TKqN2a+9U8mgiP9dOR2JNW/ErnH0xgYNRS0Di1hdIY+7HylDCrP3LqLPVm7rhCcl
K3gfsVPd4yDUtBqjfKtZgwKY4BKZR9qIeVAA3l+1Sx/qhtyJ7MN2Ni8eZjJNssBd
QLbUWBgsu3fDyrPC2FFrZ5zRp5cRVebPPEZToyaRgnhhQGOUCyQDkBwN+7TOhk1D
xZtdq/Y7Rs28sy6ornEQbLeWf2X8M7AWwoM9fbmpM/spZUSE1VFMNC99abyb2XcE
44iG6Nj6FJNeSOaM5o9ta5XV8FHLJxVQwTY0YrSdIovUYkF2dC6P4YPkG6si1Ig7
TwiWvf3r9wruvUYrxroG5BJtllJ3R4rzkw5rifj+Tl60L26NHWDeeZdRU629Mvqb
bcEKAgFwov8unXbQdBUz
=fqzw
-----END PGP SIGNATURE-----

--=-vjn5HOtiE3GgsWHwUElE--


From nobody Mon Sep  5 09:00:58 2016
Return-Path: <clement.oudot@savoirfairelinux.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32610128E18 for <ldapext@ietfa.amsl.com>; Mon,  5 Sep 2016 09:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.639
X-Spam-Level: 
X-Spam-Status: No, score=-2.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJ6oyWCdvIRX for <ldapext@ietfa.amsl.com>; Mon,  5 Sep 2016 09:00:53 -0700 (PDT)
Received: from mail.savoirfairelinux.com (mail.savoirfairelinux.com [208.88.110.44]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2CAD127A90 for <ldapext@ietf.org>; Mon,  5 Sep 2016 09:00:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.savoirfairelinux.com (Postfix) with ESMTP id 6B5C76203A0 for <ldapext@ietf.org>; Mon,  5 Sep 2016 12:00:52 -0400 (EDT)
Received: from mail.savoirfairelinux.com ([127.0.0.1]) by localhost (mail.savoirfairelinux.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 2M-Wqu4uVfbS for <ldapext@ietf.org>; Mon,  5 Sep 2016 12:00:50 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by mail.savoirfairelinux.com (Postfix) with ESMTP id AAA1D6204C6 for <ldapext@ietf.org>; Mon,  5 Sep 2016 12:00:50 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.savoirfairelinux.com
Received: from mail.savoirfairelinux.com ([127.0.0.1]) by localhost (mail.savoirfairelinux.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8-MPKJKqzYDT for <ldapext@ietf.org>; Mon,  5 Sep 2016 12:00:50 -0400 (EDT)
Received: from [192.168.47.134] (LStLambert-656-1-262-71.w193-248.abo.wanadoo.fr [193.248.50.71]) by mail.savoirfairelinux.com (Postfix) with ESMTPSA id 0946C6203A0 for <ldapext@ietf.org>; Mon,  5 Sep 2016 12:00:49 -0400 (EDT)
To: ldapext@ietf.org
References: <1473028512.26123.43.camel@redhat.com>
From: =?UTF-8?Q?Cl=c3=a9ment_OUDOT?= <clement.oudot@savoirfairelinux.com>
Organization: Savoir-Faire Linux
Message-ID: <d49c35f3-6b00-614c-4ce0-5dba7d884c73@savoirfairelinux.com>
Date: Mon, 5 Sep 2016 18:00:47 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <1473028512.26123.43.camel@redhat.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/QgeFPgy9blmfZEWMsg4s2y7a8H8>
Subject: Re: [ldapext] Request for feedback: draft-wibrown-ldapssotoken
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Sep 2016 16:00:56 -0000

Le 05/09/2016 =E0 00:35, William Brown a =E9crit :
> Hi,
>
> I would like to ask for feedback on the submission
> draft-wibrown-ldapssotoken [0]. Section 5 deals with the ldap component=
s
> of the implementation.
>
> Thank you for your time and advice,
>
> [0] https://datatracker.ietf.org/doc/draft-wibrown-ldapssotoken/
>

Hi,

this draft is really interesting and indeed provides a solution when no=20
Kerberos is available.

I was wondering if we could not get quite same behavior with proxy=20
authentication and standard single-sign on mechanisms: the user is known=20
by the web application trough token (JWT or whatever) and then the web=20
application authenticates for this user using LDAP proxy authz.

Other remark, you don't give any hint on how the LDAP server should=20
manage its token database. Maybe it is intended as each LDAP server=20
should implement its own way, but we may think of standard LDAP objects=20
that could be used to manage these tokens directly in LDAP, instead of=20
using a separate database?

Regards,

--=20
Cl=E9ment OUDOT
Consultant en logiciels libres, Expert infrastructure et s=E9curit=E9
Savoir-faire Linux

