[jboss-dev-forums] [JBoss AS 7 Development] - Re: Every single remote ejb call starts full authentication process with SecurityDomain cache-type="default"

[Robert Marcano]

Robert Marcano [https://community.jboss.org/people/robmv] created the discussion

"Re: Every single remote ejb call starts full authentication process with SecurityDomain cache-type="default""

To view the discussion, visit: https://community.jboss.org/message/744110#744110

--------------------------------------------------------------
> Michael Gronau wrote:
> 
> Hello Darran,
> I've tried the current 7.1.2 build, but the problem still exists. Is it correct, that the caching only works, when I extend my login module from a Jboss specific login module (this is not suitable for our app so far.)?
Do your login module adds CallerPrincipal the way JBoss login modules require? I have another problem related to how caching works. If you are creating a Principal on your login module and not adding it to CallerPrincipal or your principal has a different name or class than an internal JBoss remoting principal instance (See RemotingLoginModule), then caching doesn't work as expected  https://community.jboss.org/thread/201664 https://community.jboss.org/thread/201664

Your login module must understand password-stacking for remoting authentication to work correctly and be cached, AbstractServerLoginModule JBoss implementation helps a lot in providing the basic code to have a correct password-stacking behavior
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/744110#744110]

Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20120625/38c53b4c/attachment.html