From: Justin B. <jb...@ec...> - 2010-12-09 14:06:08
|
Hi, In webapps/gridsam/WEB-INF/classes/GridSAMService.properties you will find a property called allowUnauthorised. Try setting this to be 'true', as it is 'false' by default. Restart your container and see if this fixes your problem. Regards, Justin On 9 Dec 2010, at 09:45, I. Marín Carrión wrote: > Dear all, > > this is a grid developer from Complutense University of Madrid, Spain. > > We are using GridSAM as testing platform for our BES clients. These > clients do not use any authentication method (for now) and so we have > disabled any security mechanism from GridSAM. Thus, we comment the > section from server-config.wsdd where "<!-- BES with OMII WS-Security > -->" and uncomment where "<!-- BES withOut OMII WS-Security + > Username/Password -->", but commenting also in this section the next > lines: > > <!--<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver"> > <parameter name="action" value="UsernameToken"/> > <parameter name="passwordCallbackClass" > value="org.icenigrid.gridsam.bes.webservice.common.PWCallback"/> > </handler>--> > > > However, when I try to submit a job using my own client, this provides > an security exception: "java.lang.SecurityException: attempting to add > an object which is not an instance of java.security.Principal to a > Subject's Principal Set", which is thrown by > org/apache/axis/client/Call.invoke(). > > Therefore, Should I make some changes more to disable any security > mechanism of GridSAM/BES? > > Best regards. > > > ------------------------------------------------------------------------------ > This SF Dev2Dev email is sponsored by: > > WikiLeaks The End of the Free Internet > http://p.sf.net/sfu/therealnews-com > _______________________________________________ > GridSAM-Discuss mailing list > Gri...@li... > https://lists.sourceforge.net/lists/listinfo/gridsam-discuss -- Justin Bradley Senior Software Consultant jb...@ec... OMII-UK / EPrints Services Bay 22, 4067, B32 University of Southampton |