X-Original-To: alpine-infra@alpinelinux.org
Delivered-To: alpine-infra@mail.alpinelinux.org
Received: from mail-fx0-f43.google.com (mail-fx0-f43.google.com [209.85.161.43])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mail.alpinelinux.org (Postfix) with ESMTPS id 1A72CDC007B;
	Wed, 16 Nov 2011 12:51:17 +0000 (UTC)
Received: by faan24 with SMTP id n24so1905197faa.30
        for <multiple recipients>; Wed, 16 Nov 2011 04:51:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        bh=rTeFPdmrbewnxey5wuOc4ykOfrJ+1uyEdWvFYg2EV34=;
        b=q/yG3BvrOLC8IorSLhN2cxUv45ORiQQA28jbFjCtQL+Y5EvTtb/bBHIe3Evmn8NVYF
         skkJF0ki53qN4rQh4WTpcjZfcWmOEoqNlVAWP9nbdz4TvUfnJR9e7BGrZarGW6+dIbGO
         ENnTYpeDWQZQLX2m+I00H8aUMzoBYQetdd9BA=
MIME-Version: 1.0
Received: by 10.182.212.33 with SMTP id nh1mr7039432obc.72.1321447876275; Wed,
 16 Nov 2011 04:51:16 -0800 (PST)
Received: by 10.182.121.38 with HTTP; Wed, 16 Nov 2011 04:51:16 -0800 (PST)
In-Reply-To: <20111116131921.34638e1b@ncopa-desktop.nor.wtbts.net>
References: <20111116105206.6380417a@ncopa-desktop.nor.wtbts.net>
	<CAHwjr354yPwTSOfAT1wZK7PzmpeoJa+Vq4F_fj+Ppt+KyEOOxQ@mail.gmail.com>
	<20111116131921.34638e1b@ncopa-desktop.nor.wtbts.net>
Date: Wed, 16 Nov 2011 07:51:16 -0500
Message-ID: <CAHwjr37SgrmAng8fc=H7FZXtaH01U5hqzr=W011S9Noqmxo=nw@mail.gmail.com>
Subject: Re: Securepass integration for Alpine Linux
From: Jeff Bilyk <jbilyk@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-infra@alpinelinux.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 16, 2011 at 7:19 AM, Natanael Copa <ncopa@alpinelinux.org> wrot=
e:
> On Wed, 16 Nov 2011 06:54:23 -0500
> Jeff Bilyk <jbilyk@gmail.com> 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 think doing it properly would be nice.  Also, we seem to be getting
a fair amount of marketing right now, not sure we need much more...
don't want to stretch too thin too fast, but maybe I'm over-worrying
that.

>
>> 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. =A0We 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.

Re: simple/polished account creation: agreed.  I haven't tested
password reset yet, but will do so before rolling anything out.

>
> -nc
>
>
--=20
Jeff