10:48 p.m.
SOA-P5 , Security , and the ESB XML in JBDS 3.0
-----------------------------------------------
Key: JBDS-1167
URL: https://jira.jboss.org/jira/browse/JBDS-1167
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Affects Versions: 3.0.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
7 a.m.
New subject: [JBoss JIRA] Moved: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plu...
]
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
7:57 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-6160:
---------------------------------------
Fix Version/s: 3.2.next
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
Fix For: 3.2.next
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
7:59 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-6160:
---------------------------------------
Component/s: esb
Assignee: Brian Fitzpatrick
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
Components: esb
Affects Versions: 3.1.0.CR1
Reporter: Gary Lamperillo
Assignee: Brian Fitzpatrick
Fix For: 3.2.next
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
10:07 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-6160:
------------------------------------------
Gary, is there any documentation on these settings you can point us to for further
information?
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
Components: esb
Affects Versions: 3.1.0.CR1
Reporter: Gary Lamperillo
Assignee: Brian Fitzpatrick
Fix For: 3.2.next
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
7:33 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plu...
]
Gary Lamperillo commented on JBIDE-6160:
----------------------------------------
Hi Brian,
Only documentation is in the quick start that I know of. In the form of code :)
You may want to have a discussion with Anil on this.
Thanks,
Gary
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
Components: esb
Affects Versions: 3.1.0.CR1
Reporter: Gary Lamperillo
Assignee: Brian Fitzpatrick
Fix For: 3.2.next
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
9:29 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/jira/browse/JBIDE-6160?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-6160:
------------------------------------------
Thanks Gary, I've sent an e-mail along to Anil to kick off this conversation and will
try to capture the results in JIRA.
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
Components: esb
Affects Versions: 3.1.0.CR1
Reporter: Gary Lamperillo
Assignee: Brian Fitzpatrick
Fix For: 3.2.next
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
8:09 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6160:
------------------------------------------
Never heard back from Anil in May, so sent another e-mail today...
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: Brian Fitzpatrick
Fix For: 3.2.x
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
10:27 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6160:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Looks like this has been handled to some degree with Slava's changes for JBIDE-6758.
I've asked Len & Babak to chime in on any additional changes that should be made
to support the Security tag in the editor.
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: Brian Fitzpatrick
Fix For: 3.2.x
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
11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Gary Lamperillo commented on JBIDE-6160:
----------------------------------------
Yes, I agree Slava's Security change solves this. Can We add that the
"org.jboss.soa.esb.services.security.auth.login.JBossSTSIssueCallbackHandler" be
available as a value in the select box?
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: Brian Fitzpatrick
Fix For: 3.2.x
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
11:25 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6160:
------------------------------------------
Just to clarify... Is that the class that the callback handler needs to extend? Or just
the option that's available out of the box?
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: Brian Fitzpatrick
Fix For: 3.2.x
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
11:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Gary Lamperillo commented on JBIDE-6160:
----------------------------------------
Hi Brian,
As referenced above, it is the callbackhandler needed for the example. I would guess in
some cases it may need to be extended. Someone from the Picketlink may have a better
idea.
Regards,
Gary
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: Brian Fitzpatrick
Fix For: 3.2.x
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
11:15 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6160:
-------------------------------------
Assignee: Viacheslav Kabanovich (was: Brian Fitzpatrick)
Fix Version/s: 3.2.0.M2
(was: 3.2.x)
Slava, can we add
"org.jboss.soa.esb.services.security.auth.login.JBossSTSIssueCallbackHandler" as
a value to the Callback Handler drop-down box?
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
5:13 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
Viacheslav Kabanovich resolved JBIDE-6160.
------------------------------------------
Resolution: Done
Brian, I have added the option. Please reopen the issue if more improvements are needed.
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
8:40 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-6160) SOA-P5 , Security , and the ESB XML in JBDS 3.0
[
https://jira.jboss.org/browse/JBIDE-6160?page=com.atlassian.jira.plugin.s...
]
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
5714
days inactive
5880
days old
jbosstools-issues@lists.jboss.org
14 comments
5 participants
participants (5)
-
Brian Fitzpatrick (JIRA) -
Gary Lamperillo (JIRA)
-
Libor Zoubek (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Viacheslav Kabanovich (JIRA)