I'm able to run the Java WSCore container with no security, but I get an error when I try to start the container with a certificate. The next step will be to recreate the Linux based certificate directory structure on the Windows machine and troubleshoot from there. I will also try to load the ca-setup file from the internal grid machine.
FAILURE:
C:\gt4\bin>grid-proxy-init -debugFiles used: proxy : C:\DOCUME~1\bubba-gump\LOCALS~1\Temp\x509up_u_bubba-gump user key : C:\Documents and Settings\bubba-gump\.globus\userkey.pem user cert : C:\Documents and Settings\bubba-gump\.globus\usercert.pemYour identity: xxx xxx xxx Enter GRID pass phrase for this identity:Using 512 bits for private keyCreating proxy, please wait...Proxy verify failed: Unable to load CA ceritificatesjava.lang.Exception: Unable to load CA ceritificates at org.globus.tools.ProxyInit.verify(ProxyInit.java:131) at org.globus.tools.DefaultProxyInit.verify(ProxyInit.java:595) at org.globus.tools.ProxyInit.createProxy(ProxyInit.java:225) at org.globus.tools.ProxyInit.main(ProxyInit.java:530) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.globus.bootstrap.BootstrapBase.launch(BootstrapBase.java:114) at org.globus.bootstrap.Bootstrap.main(Bootstrap.java:41)C:\gt4\bin>globus-start-container[JWSCORE-114] Failed to start container: [JWSCORE-200] Container failed to initialize [Caused by: [JWSSEC-248] Secure container requires valid credentials. No container descriptor file configured and default proxy not found. Run grid-proxy-init to create default proxy credential.]
SUCCESS:
C:\gt4\bin>globus-start-container -nosecStarting SOAP server at http://127.0.0.1:8080/wsrf/services/
With the following services:
[1]: http://127.0.0.1:8080/wsrf/services/AdminService[2]: http://127.0.0.1:8080/wsrf/services/AttachmentTestService[3]: http://127.0.0.1:8080/wsrf/services/AuthzCalloutTestService[4]: http://127.0.0.1:8080/wsrf/services/ContainerRegistryEntryService[5]: http://127.0.0.1:8080/wsrf/services/ContainerRegistryService[6]: http://127.0.0.1:8080/wsrf/services/CounterService[7]: http://127.0.0.1:8080/wsrf/services/DeployService[8]: http://127.0.0.1:8080/wsrf/services/JWSCoreVersion[9]: http://127.0.0.1:8080/wsrf/services/LoggingService[10]: http://127.0.0.1:8080/wsrf/services/ManagementService[11]: http://127.0.0.1:8080/wsrf/services/NotificationConsumerFactoryService[12]: http://127.0.0.1:8080/wsrf/services/NotificationConsumerService[13]: http://127.0.0.1:8080/wsrf/services/NotificationTestService[14]: http://127.0.0.1:8080/wsrf/services/PersistenceTestSubscriptionManager[15]: http://127.0.0.1:8080/wsrf/services/QueryTestService[16]: http://127.0.0.1:8080/wsrf/services/RPParamTestService[17]: http://127.0.0.1:8080/wsrf/services/SAMLAuthzTestService[18]: http://127.0.0.1:8080/wsrf/services/SampleAuthzService[19]: http://127.0.0.1:8080/wsrf/services/SecureCounterService[20]: http://127.0.0.1:8080/wsrf/services/SecurityTestService[21]: http://127.0.0.1:8080/wsrf/services/ShutdownService[22]: http://127.0.0.1:8080/wsrf/services/SubscriptionManagerService[23]: http://127.0.0.1:8080/wsrf/services/TestAuthzService[24]: http://127.0.0.1:8080/wsrf/services/TestEnumService[25]: http://127.0.0.1:8080/wsrf/services/TestLoginModuleService[26]: http://127.0.0.1:8080/wsrf/services/TestParamAuthzService[27]: http://127.0.0.1:8080/wsrf/services/TestRPCService[28]: http://127.0.0.1:8080/wsrf/services/TestService[29]: http://127.0.0.1:8080/wsrf/services/TestServiceRequest[30]: http://127.0.0.1:8080/wsrf/services/TestServiceWrongWSDL[31]: http://127.0.0.1:8080/wsrf/services/Version[32]: http://127.0.0.1:8080/wsrf/services/WidgetNotificationService[33]: http://127.0.0.1:8080/wsrf/services/WidgetService[34]: http://127.0.0.1:8080/wsrf/services/gsi/AuthenticationService
Monday, November 10, 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment