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

[Paul Gier (JIRA)]

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

Paul Gier commented on JBAS-7010:
---------------------------------

I checked out the branch and built the whole thing from the root directory.  It built ok for me, so I'm deploying an update to the snapshot repository now.
Scott, it might have failed for you if you tried building only the security module since the snapshot dependencies that were being retrieved were so old.

Any reason you are not using the default local repo location (.m2/repository) ?  If you have your local repo and the svn checkout in the same place it might cause problems.

> 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: Paul Gier
>             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