That worked! Thanks a lot! I'll submit a patch of the tomcat valve to the BlazeDS project. It would be great to see Glassfish fully supported.
--- In [email protected], "meteatamel" <[EMAIL PROTECTED]> wrote: > > Instead of server="Glassfish", can you try server="all" and let us > know if there's anything different? > > thanks, > Mete > > --- In [email protected], "cyberscriptnet" <ryan@> wrote: > > > > Hi, > > > > I've been using BlazeDS/LCDS on Glassfish without issues until now. > I'm attempting to > > enable custom authentication using TomcatLoginCommand > > > > In order for Tomcat valves to work with Glassfish I had to make > modifications to > > TomcatValve4150 described here: > > http://wiki.glassfish.java.net/Wiki.jsp?page=FaqTomcatValveConversion > > > > That compiled and deployed without problems, I even added logging > code to verify the > > valve is executed each request. > > > > My final issue is when I execute ro.setCredentials(u,p) I get the > following error on the > > server: > > "External login command required. Please check your security > configuration." > > > > I have also verified that TomcatLoginCommand.doAuthentication is not > being executed. > > > > My security configuration is: > > > > <security> > > <login-command > class="flex.messaging.security.TomcatLoginCommand" > > server="Glassfish"/> > > <security-constraint id="pos-access"> > > <auth-method>Custom</auth-method> > > <roles> > > <role>salesPerson</role> > > </roles> > > </security-constraint> > > </security> > > > > Has anyone been able to get custom authentication working with > Glassfish? > > > > Thanks! > > > > Ryan Campbell > > >
