[jbosstools-issues] [JBoss JIRA] Closed: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0

[Libor Zoubek (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Libor Zoubek closed JBIDE-6160.
-------------------------------



verified no JBDS 4.0.0 M2

> SOA-P5 , Security , and the ESB XML in JBDS 3.0
> -----------------------------------------------
>
>                 Key: JBIDE-6160
>                 URL: https://jira.jboss.org/browse/JBIDE-6160
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: esb
>    Affects Versions: 3.1.0.CR1
>            Reporter: Gary Lamperillo
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.2.0.M2
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira