0 Replies Latest reply on Dec 8, 2002 4:23 PM by Volkmar

    Authentication issues with standalone client/intra-bean comm

    Volkmar Newbie

      Hello everyone,

      I hope someone can give me some hints on the following:
      I have deployed an application with a standalone client successfully; the security that I intended to use for the initial test phase were none, i.e. I gave all methods in the ejb-jar.xml file the unchecked option.
      As far as the initial screen and the instantiation of a stateless session bean goes, this seems to work with no problems. However, when I try to call another EJB's create methods from that session bean, it throws a 'No security context set ' exception. I can understand this to a certain extent, in that I haven't configured a security domain/haven't authenticated myself to the server, but since I have declared all methods' security as 'unchecked' (including create), that shouldn't make a difference ?!?
      Obviously it does, but I can't find a way to get around it. Ultimately I will have to secure the app properly, but to test a few things under JBoss first, I'd like to have a play around with full access to all the functionality...
      Can anyone point me in the right direction ?



      P.S. If needed, I will post any config files you'd like to see.