[
https://jira.jboss.org/browse/SEAMSECURITY-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Bryzak moved JBSEAM-4559 to SEAMSECURITY-17:
--------------------------------------------------
Project: Seam Security (was: Seam)
Key: SEAMSECURITY-17 (was: JBSEAM-4559)
Component/s: (was: Security)
Fix Version/s: 3.0.0.Beta1
(was: 3.0.0.BETA1)
> Servlet Filter to pick up security information for Seam after Java EE web
> container security
> --------------------------------------------------------------------------------------------
>
> Key: SEAMSECURITY-17
> URL: https://jira.jboss.org/browse/SEAMSECURITY-17
> Project: Seam Security
> Issue Type: Feature Request
> Reporter: Anil Saldhana
> Assignee: Shane Bryzak
> Fix For: 3.0.0.Beta1
>
>
> Shane, as discussed, it will be beneficial to have a Servlet Filter that
> populates the seam security layer with the results of the Web Container
> security enforced by the servlet container. This will not only allow seam
> users to utilize the Servlet Spec mandated FORM, BASIC, CLIENT-CERT, DIGEST
> forms of authentication but also utilize features such as SPNego (via JBoss
> Negotiation) out of the box with minimal configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
