X-Original-To: alpine-infra@alpinelinux.org Delivered-To: alpine-infra@mail.alpinelinux.org Received: from mail.wtbts.no (mail.wtbts.no [213.234.126.131]) by mail.alpinelinux.org (Postfix) with ESMTP id 6D888DC007B for ; Wed, 16 Nov 2011 12:19:24 +0000 (UTC) Received: from localhost (bsna.nor.wtbts.net [127.0.0.1]) by mail.wtbts.no (Postfix) with ESMTP id 4B2D7AE4004; Wed, 16 Nov 2011 12:19:23 +0000 (UTC) X-Virus-Scanned: Yes Received: from mail.wtbts.no ([127.0.0.1]) by localhost (bsna.nor.wtbts.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9V7KRYTuq4AW; Wed, 16 Nov 2011 12:19:22 +0000 (UTC) Received: from mail.ytre.org (extmail.nor.wtbts.net [10.65.72.14]) by mail.wtbts.no (Postfix) with ESMTP id 31051AE4001; Wed, 16 Nov 2011 12:19:22 +0000 (UTC) Received: from mail.ytre.org (localhost [127.0.0.1]) by mail.ytre.org (Postfix) with ESMTP id 130BB6167D351; Wed, 16 Nov 2011 12:19:22 +0000 (UTC) Received: from ncopa-desktop.nor.wtbts.net (ncopa-desktop.nor.wtbts.net [10.65.65.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ncopa@ytre.org) by mail.ytre.org (Postfix) with ESMTPSA id D77B760AB6E32; Wed, 16 Nov 2011 12:19:21 +0000 (UTC) Date: Wed, 16 Nov 2011 13:19:21 +0100 From: Natanael Copa To: Jeff Bilyk Cc: alpine-infra@alpinelinux.org Subject: Re: Securepass integration for Alpine Linux Message-ID: <20111116131921.34638e1b@ncopa-desktop.nor.wtbts.net> In-Reply-To: References: <20111116105206.6380417a@ncopa-desktop.nor.wtbts.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP On Wed, 16 Nov 2011 06:54:23 -0500 Jeff Bilyk wrote: > Hi Natanael, > > If all we're going to be using it for is SSO, then I'd prefer to keep > that type of infra in-house (my 2cents). +1 I still ask since this might be a "lazy" way out of it and might give us some marketing > I've got a setup for ldap > figured out now with openldap + phpldapadmin that'll run on one box, > but just need to polish it a bit before deploying to a primary and > backup a.o server. We could then use that for SSO for a.o services. great! I'm mostly worried about a polished user account creation and password reset mechanism. -nc