Bugzilla – Bug 5975
Container-level GS4GT inclusion causes exception
Last modified: 2008-04-25 21:12:38
You need to log in before you can comment on or make changes to this bug.
Trying to use GridShibPDP at the container level causes the appended exception. # cat /usr/local/gt-4.0.6/etc/globus_wsrf_core/global_security_descriptor.xml <?xml version="1.0" encoding="UTF-8"?> <securityConfig xmlns="http://www.globus.org"> <credential> <key-file value="/etc/grid-security/containerkey.pem"/> <cert-file value="/etc/grid-security/containercert.pem"/> </credential> <authz value="global:org.globus.gridshib.GridShibPDP"/> <!-- <authz value="global:org.globus.gridshib.SAMLAssertionPushPIP global:org.globus.gridshib.AttributeAcceptancePIP global:org.globus.gridshib.SAMLBlacklistPDP"/> --> <gridmap value="/etc/grid-security/grid-mapfile"/> </securityConfig> Container failed to initialize. Caused by java.lang.NullPointerException at org.globus.wsrf.impl.security.authorization.ContainerPDPConfig.getProperty(ContainerPDPConfig.java:41) at org.globus.gridshib.BasePDP.initialize(BasePDP.java:66) at org.globus.wsrf.impl.security.authorization.ServiceAuthorizationChain.initialize(ServiceAuthorizationChain.java:108) at org.globus.wsrf.impl.security.util.PDPUtils.getServiceAuthzChain(PDPUtils.java:114) at org.globus.wsrf.impl.security.util.PDPUtils.getContainerAuthzChain(PDPUtils.java:148) at org.globus.wsrf.impl.security.descriptor.ContainerSecurityConfig.loadAuthorization(ContainerSecurityConfig.java:143) at org.globus.wsrf.impl.security.descriptor.SecurityConfig.initSecurityDescriptor(SecurityConfig.java:193) at org.globus.wsrf.impl.security.descriptor.SecurityConfig.initialize(SecurityConfig.java:171) at org.globus.wsrf.impl.security.descriptor.ContainerSecurityConfig.initialize(ContainerSecurityConfig.java:101) at org.globus.wsrf.impl.security.descriptor.ContainerSecurityConfig.getConfig(ContainerSecurityConfig.java:89) at org.globus.wsrf.impl.security.descriptor.ContainerSecurityConfig.getConfig(ContainerSecurityConfig.java:78) at org.globus.wsrf.container.GSIServiceDispatcher.init(GSIServiceContainer.java:75) at org.globus.wsrf.container.ServiceContainer.start(ServiceContainer.java:242) at org.globus.wsrf.container.ServiceContainer.<init>(ServiceContainer.java:197) at org.globus.wsrf.container.GSIServiceContainer.<init>(GSIServiceContainer.java:45) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.globus.wsrf.container.ServiceContainer.createContainer(ServiceContainer.java:138) at org.globus.wsrf.container.ServiceContainer.startSecurityContainer(ServiceContainer.java:452) at org.globus.wsrf.container.ServiceContainer.main(ServiceContainer.java:408) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.globus.bootstrap.BootstrapBase.launch(BootstrapBase.java:95) at org.globus.bootstrap.Bootstrap.main(Bootstrap.java:37)
Are there any parameters at all in the service descriptor with the "global" prefix? If not, add one and see if that makes a difference.
This is not a GridShib bug. See Bug 5976