Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 45283] Allow multiple authenticators to be added
 to pipeline
In-Reply-To: <bug-45283-78@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-Id: <20080627203739.3D378234C14F@brutus.apache.org>
Date: Fri, 27 Jun 2008 13:37:39 -0700 (PDT)

https://issues.apache.org/bugzilla/show_bug.cgi?id=45283


--- Comment #6 from Seetharama Durbha <techrams@yahoo.com>  2008-06-27 13:37:38 PST ---
(In reply to comment #4)
It is possible that Realm chaining can address the requirement - however, I
feel that the current authenticate methods in the Realm interface are too
restrictive. They need to mirror the support we have for the invoke method in
the Valve interface (that is make the request and response objects available).

The reason being that we need to be able to extend authentication beyond
username/credential/certificate. Some authentication schemes may require more
data than just these. Making the request object available will alleviate the
problem.

Also, the response behavior after a successful/failed authentication may need
to be tailored. This may require that the response object also be made
available.

Making the request and response objects available to the realm authenticators
will solve a large set of problems.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org