[jboss-jira] [JBoss JIRA] Reopened: (JBAS-7010) JndiLoginInitialContextFactory is not creating expected SecurityContext
Ian Springer (JIRA)
jira-events at lists.jboss.org
Fri Jun 12 11:12:56 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer reopened JBAS-7010:
--------------------------------
Scott, I'm using the latest from the EAP branch and am still getting the "Caller unauthorized" error. The client I'm using is at https://svn.jboss.org/repos/jopr/trunk/etc/jbas5-ejb-client/. Would you please try with my client and see if it fails for you as well, and, if so, see if you can figure out what's wrong.
> 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
More information about the jboss-jira
mailing list