From users-return-515-apmail-directory-users-archive=directory.apache.org@directory.apache.org Wed May 30 17:02:37 2007 Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 36771 invoked from network); 30 May 2007 17:02:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2007 17:02:35 -0000 Received: (qmail 1240 invoked by uid 500); 30 May 2007 17:02:30 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 1184 invoked by uid 500); 30 May 2007 17:02:30 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 1144 invoked by uid 99); 30 May 2007 17:02:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 10:02:29 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 209.85.132.244 as permitted sender) Received: from [209.85.132.244] (HELO an-out-0708.google.com) (209.85.132.244) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 10:02:25 -0700 Received: by an-out-0708.google.com with SMTP id c31so719166ana for ; Wed, 30 May 2007 10:01:57 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=pn5qzn60GOi9c8ciweaUNjKg06rik5SRd9EgA9fTe6LTaMMbIi64q/EJsTKWR0+AYJPsh5GAGHQpFtzQGe8wCBdgzCI4b6pIIdHSneIQOFDoQWYSlh/YgVJ3DmZ3da66iq5irZGKOv5ymjoSYidYGAWLj1xZSucVE4LYvIkSwM0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=cJ+qMBxupIoUf3xtOklB+a0CiWhVycIHBcL8QRm1H7LIkC+sWNkwfF+ocDQegV5s2/ZKqF7dE9dBvXCQ/6KBk17+iDCrVDl2b/DO5QWo2x7AwJDTzrjGSStHdvg5SWobFXUFR6opWgh4p3BXXkMrcAuYT2K9hQEzUo+/Rt0C+3c= Received: by 10.143.166.20 with SMTP id t20mr288457wfo.1180544516494; Wed, 30 May 2007 10:01:56 -0700 (PDT) Received: by 10.142.101.21 with HTTP; Wed, 30 May 2007 10:01:56 -0700 (PDT) Message-ID: Date: Wed, 30 May 2007 13:01:56 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: users@directory.apache.org Subject: Re: Triplesec in production In-Reply-To: <4ec1f3600705300657y4304ce9cgc998f249ef384ef8@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4909_6359013.1180544516468" References: <4ec1f3600705300657y4304ce9cgc998f249ef384ef8@mail.gmail.com> X-Google-Sender-Auth: 5e2903111856f945 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4909_6359013.1180544516468 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sure. I have it in production in a couple places now but I cannot really talk too much about it in a public forum. You can contact me though at akarasulu@gmail.com. Alex On 5/30/07, bb.boogie@gmail.com wrote: > > Hello group, > > I have a client that is interested in triplesec as a strong authentication > solution. We currently have it running in house, as well as at one other > client in a development environment. My client is interested to chatting > with anyone who is actively running triplesec in a live production > environment. Would anyone in this group be willing to speak wih them about > pros/cons, issues encountered, stability, etc.? I appreciate anyone would > would be willing to do so. Thank you. > > Rockie > ------=_Part_4909_6359013.1180544516468--