[
https://issues.apache.org/jira/browse/GERONIMO-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783414#comment-13783414
]
Arjan Tijms commented on GERONIMO-6423:
---------------------------------------
I wonder if there is any progress here. This is still a rather serious
impediment for using JASPIC on Geronimo.
> Programmatically registering JASPIC auth module doesn't work correctly
> ----------------------------------------------------------------------
>
> Key: GERONIMO-6423
> URL: https://issues.apache.org/jira/browse/GERONIMO-6423
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, Jetty, Tomcat
> Affects Versions: 3.0.0
> Reporter: Arjan Tijms
> Labels: jaspic, security
>
> JASPIC defines an API via which a Server Authentication Module (SAM) can be
> programmatically registered.
> This works on JBoss AS, GlassFish and WebLogic, but not entirely correct on
> Geronimo V3.0. It only works if Geronimo is started with the application that
> does this registering deployed, then undeploy that app and immediately deploy
> it again.
> See
> http://arjan-tijms.blogspot.com/2012/11/implementing-container-authentication.html
> for further details.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
