[JBoss JIRA] Created: (JBESB-2958) Change security for default if in embedded server
by Kevin Conner (JIRA)
Change security for default if in embedded server
-------------------------------------------------
Key: JBESB-2958
URL: https://jira.jboss.org/jira/browse/JBESB-2958
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.7
Reporter: Kevin Conner
Fix For: 4.7
Up to this point, the 'default' server has always been unsecured and 'production' secured.
This has now changed on the platform to the following
standalone (esb) server
- default server, unsecured
embedded (app server) server
- default server, secured (also default config)
- production server, secured
We need to change the identification of 'production' in the base-build.xml so that it always attempts secure access if within the full SOA server. The following should be sufficient.
@@ -335,7 +335,7 @@
<target name="dependencies" depends="classpath-dependencies-as4, classpath-dependencies-as5, quickstart-specific-checks">
<condition property="jbossesb-server-production">
- <equals arg1="${org.jboss.esb.server.config}" arg2="production"/>
+ <available file="${product.dir}/server/production"/>
</condition>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2957) extraneous xmlsec jar causes WSSecurityException
by David Ward (JIRA)
extraneous xmlsec jar causes WSSecurityException
------------------------------------------------
Key: JBESB-2957
URL: https://jira.jboss.org/jira/browse/JBESB-2957
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples, Security, Web Services
Affects Versions: 4.7
Environment: both AS4+Java5 and AS5+Java6
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When running the webservice_wssecurity quickstart, the following failure occurs:
09:59:19,958 ERROR [WSSecurityDispatcher] Internal error occured handling inbound message:
org.jboss.ws.extensions.security.exception.WSSecurityException: Could not parse encrypted key: No message with ID "XMLCipher unexpectedly not in UNWRAP_MODE or DECRYPT_MODE..." found in resource bundle "org/apache/xml/security/resource/xmlsecurity"
at org.jboss.ws.extensions.security.element.EncryptedKey.<init>(EncryptedKey.java:100)
at org.jboss.ws.extensions.security.element.SecurityHeader.<init>(SecurityHeader.java:89)
at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:175)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:219)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:83)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:97)
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:127)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:171)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:187)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:586)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:420)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.xml.security.encryption.XMLEncryptionException: No message with ID "XMLCipher unexpectedly not in UNWRAP_MODE or DECRYPT_MODE..." found in resource bundle "org/apache/xml/security/resource/xmlsecurity"
at org.apache.xml.security.encryption.XMLCipher.loadEncryptedKey(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.loadEncryptedKey(Unknown Source)
at org.jboss.ws.extensions.security.element.EncryptedKey.<init>(EncryptedKey.java:96)
... 23 more
To fix this, jbossesb-server-4.6/server/default/lib/xmlsec-1.4.3.jar needs to be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2950) AS5 ESB web deployments broken on server re-start
by David Ward (JIRA)
AS5 ESB web deployments broken on server re-start
-------------------------------------------------
Key: JBESB-2950
URL: https://jira.jboss.org/jira/browse/JBESB-2950
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment, Examples
Affects Versions: 4.7
Environment: ESB 4.7 (trunk) deployed into JBoss AS 5.1.0 (running on JDK 1.6, although that part shouldn't matter)
Reporter: David Ward
Fix For: 4.7
This is a problem on ESB 4.7 (trunk) deployed into JBoss AS 5.1.0. It is *not* a problem on ESB 4.7 (trunk) deployed into JBoss AS 4.2.3.
If you have the ESB server running, and hot-deploy either the http_gateway (uses the HttpGatewayServlet) or the publish_as_webservice (uses EBWS) quickstart, everything works fine. However, if you leave the quickstart deployed, then stop and re-start the server, then although no errors appear in the log, those HTTP "endpoints" are not available. For example, if you try hitting http://localhost:8080/Quickstart_http_gateway/http/sales in a web browser after a restart, you get a 404 status error.
I chatted briefly with TomF about this, and he thinks there might be an issue with the EsbWebServiceDeployer or related web metadata / web model, or undeploy code?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months