You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2012/06/13 03:11:42 UTC

[jira] [Resolved] (GERONIMO-6338) jaspic requirements on CallbackHandler processing of CallerPrincipalCallback not implemented

     [ https://issues.apache.org/jira/browse/GERONIMO-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Forrest Xia resolved GERONIMO-6338.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0
         Assignee: David Jencks

I think this jira has been fixed in 3.0-beta branch, so set it to resolved. If any different thought, feel free to reopen it. thanks!
                
> jaspic requirements on CallbackHandler processing of CallerPrincipalCallback not implemented
> --------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6338
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6338
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector, Jetty, Tomcat
>    Affects Versions: 2.2.1, 3.0-beta-1
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> The container's CallbackHandler is supposed to establish the caller principal in the provided Subject from the principal or principal name in the CallerPrincipalCallback. See pp 90 and 91 of the jaspic 1.0 spec.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira