[
https://jira.jboss.org/jira/browse/JBDS-1169?page=com.atlassian.jira.plug...
]
Gary Lamperillo commented on JBDS-1169:
---------------------------------------
Hi Max,
I believe it is a combination of both. The SOA-P Product Team should provide the JBoss
Dev Studio the necessary pieces. PicketLink is Tech Preview in SOA-P 5. The Sequence
Diagram is the product of reverse engineering the quickstart for SAML Security. So, the
SOA-P5 team did provide a sample, whether that is enough to develop the tooling is another
question(ie, actions discussed). Given that the quickstart flow does not send the message
back to the client, besides an ack, should the quickstart be modified is another
question.
Regards,
Gary
PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action
design)
----------------------------------------------------------------------------
Key: JBDS-1169
URL:
https://jira.jboss.org/jira/browse/JBDS-1169
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: SOA Platform
Reporter: Gary Lamperillo
Assignee: Brian Fitzpatrick
Fix For: LATER
Attachments: SequenceDiagram_PicketLink.pdf
With the PicketLink and SOA-P 5 quickstart sample (security_saml), a client requests a
web service and immediately receives an acknowledgement back. A more realistic use case
would be to request a token and use it for the request using a chainhandler. SOA-P 5 can
still be utilized as the intermediate. There are a few additional pieces that are needed.
The SOA-P 5 needs a Service which forwards issue requests to PicketLink and then sends
the Token client. SOA-P 5 needs another service that validates the tokens in the requests
and either forwards the request or logs the exception and send error to the client. Both
of these services should be implemented as new actions, and should be available in the ESB
Actions as "Security Services". In addition, the current implementation
requires smooks to add the assertion to the out going message. While the internal
implementation using smooks is fine, it should not be required by the user to deal with
these internals. In the new "Security Services" section a "Add
Assertion" should be available.
--
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