Return-Path: Delivered-To: apmail-shiro-user-archive@www.apache.org Received: (qmail 48833 invoked from network); 10 Mar 2011 17:33:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Mar 2011 17:33:37 -0000 Received: (qmail 93739 invoked by uid 500); 10 Mar 2011 17:33:37 -0000 Delivered-To: apmail-shiro-user-archive@shiro.apache.org Received: (qmail 93722 invoked by uid 500); 10 Mar 2011 17:33:37 -0000 Mailing-List: contact user-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@shiro.apache.org Delivered-To: mailing list user@shiro.apache.org Received: (qmail 93714 invoked by uid 99); 10 Mar 2011 17:33:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2011 17:33:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of henry.saputra@gmail.com designates 209.85.214.45 as permitted sender) Received: from [209.85.214.45] (HELO mail-bw0-f45.google.com) (209.85.214.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2011 17:33:30 +0000 Received: by bwz16 with SMTP id 16so2329520bwz.32 for ; Thu, 10 Mar 2011 09:33:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=iEYKwxm5/lOCJE7K2Kq6RJ0abIQchFSqPIH754sNAD0=; b=ABOsQKeWP8y9o1GIvMnY3eq7c86hAtJTeY261B0MZzoxvUSDOnMY0UTxnFJx3iqwul UvywLs+PP7PiCZiyeDOX0dy9mjAPcyJjFo/Os3xhp+H8N0/PCV4XSWExGIK3qwavfTcv eqgsMs50CN/ESDO/sLVvvk6z8lhzwojz9g5lM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=T3CY1uSOuRLs2Hri7GPBn+lUz0Rfj7HYDz89Dbxr7VP4AaZ0Xi5RVBWtBleu0S5t/D lZa7dW4JYdYqXH5pBv/Gx1XWDF2NveAH1B1p5g5mXOYJLYuprCfmPmo3f5ivH/ewtdCE RdhVFBF2ITxgu7Ie6cZQybuPTPzbMZ/zophGg= MIME-Version: 1.0 Received: by 10.204.127.29 with SMTP id e29mr1130024bks.52.1299778388941; Thu, 10 Mar 2011 09:33:08 -0800 (PST) Received: by 10.204.17.9 with HTTP; Thu, 10 Mar 2011 09:33:08 -0800 (PST) Date: Thu, 10 Mar 2011 09:33:08 -0800 Message-ID: Subject: How to add existing application login method in the authenticating flow with Shiro? From: Henry Saputra To: user@shiro.apache.org Content-Type: text/plain; charset=UTF-8 Hi Shiro Community, I am planning to use Shiro to do user authentication for web services accesses and would like to get some advice on how incorporate my application custom login method into the Shiro authentication flow? I was thinking about either extending the DelegatingSubject to override login() method, or just do the login in my custom Realm.doGetAuthenticationInfo() method? Appreciate any input or help. -- Thanks, Henry