On Friday 22 February 2008 15:20, Joao Marcelo wrote: > Here is the output > > [EMAIL PROTECTED]:/usr/local/globus$ bin/globus-start-container -nosec > Failed to start container: Failed to initialize > 'WidgetNotificationService' service [Caused by: [SEC] Service > credentials not configured and was not able to obtain container > credentials.; nested exception is: > org.globus.wsrf.security.SecurityException: [SEC] Error > obtaining container credentials; nested exception is: > org.globus.wsrf.config.ConfigException: Failed to initialize > container security config file > "etc/globus_wsrf_core/global_security_descriptor.xml" [Caused by: > [Caused by: Failed to load credentials. [Caused by: > /etc/grid-security/containercert.pem (No such file or directory)]]]] > > > Even with -nosec, it still complains about certficates. > > On Fri, Feb 22, 2008 at 11:17 AM, Tobias Kunz <[EMAIL PROTECTED]> wrote: > > Hi, > > > > that's quite simple. Just use the option -nosec with > > globus-start-container. > > > > Greets, > > Tobias K. > > > > Joao Marcelo schrieb: > > Hi, > > > > Is there a way of running the WS Java Container without creating the > > certificates at /etc/grid-security? > > > > []'s
Hi Joao, Tobias, it's not possible to start the Container without certificates (-nosec just disables Transport Level Security (GSI Secure Transport), *not* Message Level (GSI Secure Conversation / GSI Secure Message) Security. -- from the desk of Tim München M.Sc. University of Applied Sciences, Muenster, Germany Department of Electrical Engineering and Computer Sciences Stegerwaldstr. 39 48565 Steinfurt EMail: [EMAIL PROTECTED] Office: +49 (0)2551 962582
