[Security & JAAS/JBoss] - OpenDS Exceprion during startup.
by paramsevak
I am currently evaluating JBOSS SSO with jboss-epp-4.3. Mainly I need to verify JBossSSO can handle ....
1- Application SSO for applications deployed on the same server
2- Application SSO for applications deployed on different servers
3- SSO for the JBoss Portal
4- SSO for the portlets deployed within the portal
I have tried working with the stable and beta releases, only to run into bugs that have yet to be fixed. Therefore now I moved to the latest source from SVN. I have been able to get further along. However I am currently getting the following error during server startup
16:14:01,814 ERROR [OpenDSManager] org.jboss.security.idm.OpenDSManager
| org.opends.server.types.InitializationException: An error occurred at or near line 5 while trying to parse the configuration from LDIF file C:\jboss-epp-4.3\jboss-as\server\default\data\opends\config\config.ldif: org.opends.server.util.LDIFException: Entry cn=config read from LDIF starting at line 5 is not valid because it violates the server's schema configuration: Entry cn=config violates the Directory Server schema configuration because it contains an unknown objectclass ds-cfg-root-config
| at org.opends.server.extensions.ConfigFileHandler.initializeConfigHandler(ConfigFileHandler.java:384)
| at org.opends.server.core.DirectoryServer.initializeSchema(DirectoryServer.java:2383)
| at org.opends.server.core.DirectoryServer.startServer(DirectoryServer.java:1305)
| at org.opends.server.util.EmbeddedUtils.startServer(EmbeddedUtils.java:89)
| at org.jboss.security.idm.OpenDSManager.start(OpenDSManager.java:116)
| 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:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| 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:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| 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:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: org.opends.server.util.LDIFException: Entry cn=config read from LDIF starting at line 5 is not valid because it violates the server's schema configuration: Entry cn=config violates the Directory Server schema configuration because it contains an unknown objectclass ds-cfg-root-config
| at org.opends.server.util.LDIFReader.readEntry(LDIFReader.java:339)
| at org.opends.server.extensions.ConfigFileHandler.initializeConfigHandler(ConfigFileHandler.java:361)
| ... 98 more
So far, I have used 'build installPortal' command to install the jboss-portal.sar and jboss-sso.sar to the server's deploy directory. Without much documentation, I can only guess this command installs portal-integration resources/classes to the server.
Can someone more familiar with the project provide some guidelines.
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225508#4225508
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225508
17 years
deployed web service consumer?
by Bogus Exception
I have deployed apps in jboss, and I like how clean they are-everything in
one place.
But now I need my apps to consume external web services. I don't want to
write a bunch of external apps in SE and have to worry about packaging them
with the JBoss JARs, not to mention the overhead and complexity of
introducing things like JCA into things. I'm really surprised a definitive
answer isn't forthcoming when searched for.
Can I write code into my beans that will go out and consume web services?
Thanks!
pat
:)
"You see, the Boyz II Men's room is flooded. 'Cause Busta Rhymes went in to
take a Master P but he got the Runs D.M.C. and had some Heavy D. And now
there's Funky Cold Medina everywhere!" -Thurgood Stubbs
17 years
[JBossWS] - SSL Client truststore
by zurchman
Is there any way to way to dynamically define a JBossWS client truststore?
I'm trying to run a standalone secure webservice client that was originally developed using a JAX-WS RI.
Using the RI, it was a simple matter to specify the truststore:
| System.setProperty("javax.net.ssl.trustStore", "path_to_my_store");
|
I've rebuilt the artifacts and application against the jbossesb-server-4.5.GA and do not seem to be able to get the client to connect to a secure endpoint.
http endpoints work fine.
Using JBossWS, I seem to get farther setting the "org.jboss.ws.wsse.trustStore" property.
The client was built from a WSDL file, and the endpoint is changed dynamically:
| BindingProvider bp = (BindingProvider) default_webservice;
| Map<String, Object> context = bp.getRequestContext();
| Object oldAddress = context.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpoint);
| System.out.println("new endpoint: " + endpoint);
|
The application fails parsing the Web service response, and I question if the request is actually connecting to service provider's SSL port.
| 2009-04-13 18:33:16,747 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: com.autowares.ipotest.Quote -> com.autowares.ipotest.Quote
| 2009-04-13 18:33:16,785 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2009-04-13 18:33:16,785 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2009-04-13 18:33:16,785 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2009-04-13 18:33:16,836 DEBUG [org.jboss.ws.core.client.HTTPRemotingConnection] Get locator for: [addr=https://service-provider-url/service-name,etc
| name={javax.xml.ws.service.endpoint.address=https://service-provider-name/service}]
| 2009-04-13 18:33:16,933 DEBUG [org.jboss.remoting.security.SSLSocketBuilder] Could not find keystore url. Can not find store file for url because store url is null.
| 2009-04-13 18:33:16,965 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker@67f39 connecting
| 2009-04-13 18:33:16,965 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker@67f39 connected
| 2009-04-13 18:33:16,965 DEBUG [org.jboss.ws.core.client.HTTPRemotingConnection] Remoting metadata: {HEADER={SOAPAction="http://qname", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true}
| 2009-04-13 18:33:16,977 DEBUG [org.jboss.ws.core.soap.SOAPContentElement]
| -----------------------------------
| 2009-04-13 18:33:16,977 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from OBJECT_VALID to XML_VALID
| 2009-04-13 18:33:16,977 DEBUG [org.jboss.ws.core.soap.ObjectContent] getXMLFragment from Object [xmlType={http://qname},javaType=class ]
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225495#4225495
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225495
17 years
[JBoss Messaging] - getting messages on one node of cluster
by mhossein
Hi:
We have a subsystem that should run only on one node (I'll call it the master node) of our cluster (right now, it's the coordinator of the cluster). We need to be able to send messages to a queue or topic from every node but we only want the node that runs the above mentioned service (the master node) to pick up those messages. (we use JBoss messaging and clustered queues for many other subsystems so we cannot set up JBoss messaging in a non-clustered way).
I originally thought that in this case, I can have that single node to subscribe to the queue programatically (instead of using MDBs) to achieve my goal. But it turned out that it's against J2EE spec to register a listener using setMessageListener inside an app server. On the other hand, if I use MDBs it means that any node may pick up any message.
Is there a way to do this? I have a few ideas but I'm not sure if they make sense or if they are at all possible:
1- Create the queue as non-clustered. Then have the "master node" put the connection factory to its own local queue on HA-JNDI and have other nodes look it up form there and send it directly to the lcoal queue of the master node (rather than using a clustered connection factory, etc)
2- Create a topic rather than a queue. This way, every node gets those messages. Then I'll make it such that a node ignores those messages unless it is the master node. But this means a lot of waste.
3- Create a queue programatically only on the master node and publish it on HA-JNDI. But then how can the master node subscribe to that programaticaly created queue ?
I'd appreciate any help on this. Sorry if my question is dumb. I'm new to JMS.
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225489#4225489
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225489
17 years
