[JBoss-user] [Security & JAAS/JBoss] - Re: JAAS Caller identity null on second EJB call in a transa

2005-11-20 Thread [EMAIL PROTECTED]
Its good your looking at the source. The unconditional push does not matter as the check for the effective run-as simply ignores nulls. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3908077#3908077 Reply to the post : http://www.jboss.com/index.html?module=b

[JBoss-user] [Security & JAAS/JBoss] - Re: JAAS Caller identity null on second EJB call in a transa

2005-11-20 Thread MClark00
I'm sure you've loved watching me have a conversation with myself, but I found the problem. In the security proxy for Session2, in the setEJBContext method, I was calling getCallerPrincipal(). Per table 3 in the EJB 2 spec, this isn't allowed. Thanks Scott, for the solution which I found in

[JBoss-user] [Security & JAAS/JBoss] - Re: JAAS Caller identity null on second EJB call in a transa

2005-11-20 Thread MClark00
I've been trying to dig through the JBoss source to understand how the caller principal is set for the home.create() call, and I think it's possible that there is a bug in the JBoss code. It's definitely possiblet hat Im wrong and I am just not understanding something correctly, but let me show