[JBoss JIRA] Created: (JBESB-2263) SAML Token support
by Jeff Yu (JIRA)
SAML Token support
------------------
Key: JBESB-2263
URL: https://jira.jboss.org/jira/browse/JBESB-2263
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 4.4 CP1
Reporter: Jeff Yu
Assignee: Jeff Yu
Fix For: 4.x
Provide support for SAML Tokens within the context of WS-Security and Single Signon.
SAML would allow Web services clients to authenticate to an Identity service, receive a SAML Token, and then use that in their subsequent Web services messages (until it expires). The ESB would then use the SAML Token to control access to ESB Services, as well as propagate to external Web services as required. One benefit of this approach it is that the client does not have to be re-authenticated with each Web service message.
--
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, 6 months
[JBoss JIRA] Created: (JBESB-2879) webservice_proxy_security works on AS4 but not AS5
by David Ward (JIRA)
webservice_proxy_security works on AS4 but not AS5
--------------------------------------------------
Key: JBESB-2879
URL: https://jira.jboss.org/jira/browse/JBESB-2879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When running the webservice_proxy_security quickstart ("ant runtest"), on AS5, this error is raised client-side (works fine on AS4):
assert-ws-available:
[echo] JBoss Webservice container found on target '/home/dward/pkgs/jboss/AS/jboss-5.1.0.GA/server/default/deploy'.
quickstart-specific-checks:
dependencies:
compile:
runinternal:
[java] **** REQUEST URL: https://localhost:8443/Quickstart_webservice_proxy_security/http/ProxyWS
[java] **** REQUEST BODY: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hello="http://webservice_proxy_security/helloworld"><soapenv:Header/><soapenv:Body><hello:sayHello><toWhom>dward</toWhom></hello:sayHello></soapenv:Body></soapenv:Envelope>
[java] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/security/plugins/FilePassword
[java] at org.jboss.soa.esb.services.security.PasswordUtil.<init>(PasswordUtil.java:59)
[java] at org.jboss.soa.esb.http.Configurator.getPasswordFromFile(Configurator.java:102)
[java] at org.jboss.soa.esb.http.configurators.HttpProtocol.getKeyMaterial(HttpProtocol.java:159)
[java] at org.jboss.soa.esb.http.configurators.HttpProtocol.configure(HttpProtocol.java:92)
[java] at org.jboss.soa.esb.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:85)
[java] at org.jboss.soa.esb.samples.quickstart.webservice_proxy_security.test.SendWSMessage.main(SendWSMessage.java:85)
BUILD FAILED
/home/dward/repos/jbossesb/trunk/product/samples/quickstarts/webservice_proxy_security/build.xml:130: The following error occurred while executing this line:
/home/dward/repos/jbossesb/trunk/product/samples/quickstarts/webservice_proxy_security/build.xml:113: Java returned: 1
--
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, 6 months
[JBoss JIRA] Created: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
by David Ward (JIRA)
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract link is missing from the contracts web application. This used to work with the old http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory, serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher, not ContractReferencePublisher, but this shouldn't matter.
--
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, 6 months