[jbosstools-issues] [JBoss JIRA] Moved: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Thu Apr 8 08:00:38 EDT 2010
[ https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Rydahl Andersen moved JBDS-1167 to JBIDE-6160:
--------------------------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-6160 (was: JBDS-1167)
Affects Version/s: 3.1.0.CR1
(was: 3.0.0.CR1)
> SOA-P5 , Security , and the ESB XML in JBDS 3.0
> -----------------------------------------------
>
> Key: JBIDE-6160
> URL: https://jira.jboss.org/jira/browse/JBIDE-6160
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Affects Versions: 3.1.0.CR1
> Reporter: Gary Lamperillo
>
> Using security setting within an ESB Service definition requires a Security element to be added. An example of this is the PicketLink sample, security_saml. When bringing this over to a JBDS project and editing the esb.xml, the only way to add the security element is to add it in the source view.
> Here is an example of the xml section to be added to a service:
> <service category="SamlSecurityQuickstart"
> description="This service demonstrates how a service can be configured to issue and validate a security token"
> invmScope="GLOBAL" name="issueTokenService">
> <security
> callbackHandler="org.jboss.soa.esb.services.security.auth.login.JBossSTSIssueCallbackHandler" moduleName="saml-issue-token">
> <!-- disable the security context timeout so that our security context is re-evaluated -->
> <property name="org.jboss.soa.esb.services.security.contextTimeout" value="0"/>
> </security>
> <listeners>
> ......
> The tooling should have "Security Settings" as an option for services.
> Also, Soap Proxy should have the addition of a "Content Type Settings" as an option to allow compatibility with endpoints.
--
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
More information about the jbosstools-issues
mailing list