users@jaspic-spec.java.net

[JIRA] Assigned: (JASPIC_SPEC-3) No portable way for auth module to ask the container to create a container authentication session

From: monzillo (JIRA) <"monzillo>
Date: Wed, 13 Feb 2013 02:53:53 +0000 (GMT+00:00)

     [ http://java.net/jira/browse/JASPIC_SPEC-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

monzillo reassigned JASPIC_SPEC-3:
----------------------------------

    Assignee: monzillo

> No portable way for auth module to ask the container to create a container authentication session
> -------------------------------------------------------------------------------------------------
>
> Key: JASPIC_SPEC-3
> URL: http://java.net/jira/browse/JASPIC_SPEC-3
> Project: jaspic-spec
> Issue Type: New Feature
> Reporter: monzillo
> Assignee: monzillo
>
> The spi is optimized for the case where the auth module is responsible for
> creating and managing authentication sessions internally and separate from
> Servlet's HttpSession machinery.
> Still there are repeated requests for this enhancement. The RI provides this
> functionality via an undocumented messageInfo flag; which when set by an auth
> module, instructs the Glassfish container to "register" and authentication
> session.
> The enhancement request is to standardize a portable means for an auth module
> to cause the encompassing container to create an authentication and to bind it
> to the response. This might be done by a flag, or by a new Callback handler, or
> perhaps by another mechanism.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira