[jboss-jira] [JBoss JIRA] Commented: (JBAS-7010) JndiLoginInitialContextFactory is not creating expected SecurityContext

[Scott M Stark (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12472348#action_12472348 ] 

Scott M Stark commented on JBAS-7010:
-------------------------------------

The problem is that the http://snapshots.jboss.org/maven2/org/jboss/jbossas/jboss-as-security/5.1.0-SNAPSHOT/ contents are not being updated. When I tried to due a deploy from the eap branch its failing to compile, so the pom is out of date. I'm working on getting the snapshot updated.

> JndiLoginInitialContextFactory is not creating expected SecurityContext
> -----------------------------------------------------------------------
>
>                 Key: JBAS-7010
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7010
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Naming, Security
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Scott M Stark
>            Assignee: Scott M Stark
>             Fix For: JBossAS-5.2.0.Beta1
>
>
> Related to JBAS-6982, a SecurityContext is not resulting from the JndiLoginInitialContextFactory operation. The result is that a SecurityContext with a null principal and credential ends up being created by the org.jboss.ejb3.security.client.SecurityClientInterceptor even though there is a non-null principal and credential available.

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