Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of suhailski@gmail.com
 designates 209.85.220.206 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=n96yTNT1PMmloe5FhK91ydEP4x2tPr+ovxPf3qafy8/LXTWPwb4Dz+6Ruw/j+sjfRc
         ev2wENREh363aU7CIYlEWD+w5xEkXPCjgPhFP6sb3Ll4Dj46zO/OO1EwkuOILpRzrEwm
         S/WFyfqb+EMd0TUeeTAjhTEgyBRTb8EtAP8PY=
MIME-Version: 1.0
Date: Mon, 19 Oct 2009 12:54:28 +0100
Message-ID: <c32d31440910190454k64d734cfk7dab0fe85d081d4a@mail.gmail.com>
Subject: Couchdb with OpenSSO
From: Suhail Ahmed <suhailski@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0015175cac2e6e481f0476486802

--0015175cac2e6e481f0476486802
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am looking to replacing my existing content management engine with
couchdb. In order to do this properly, I would have to lock down the couchdb
REST interface using OpenSSO. I would be much obliged if anyone could point
out how I should go about it. There are a number of ways OpenSSO can be
integrated, RPC/REST, SOAP, Native Java API etc. In my current system, both
authentication and authorization is performed against OpenSSO (the reason
being that the system consists of more than just the content management
engine) centrally.
Where would I go about plugging in OpenSSO? Should I do it at the Erlang
layer? The couchdb layer or the mochiweb layer?

Looking forward to hearing from you.
Thanks and cheers
su./hail

--0015175cac2e6e481f0476486802--