[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-1169) PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Thu Apr 8 08:04:24 EDT 2010


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

Max Rydahl Andersen updated JBDS-1169:
--------------------------------------

      Component/s: SOA Platform
    Fix Version/s: LATER
         Assignee: Brian Fitzpatrick


Gary, you attached a diagram with pictures but your comment refers to some specific code (I assume that is to be found inside the ESB quickstarts or )...btw. all of that would need to be exposed to the user anyway since it is not a bundled service in SOA is it ?

Shouldn't this rather be a builtin functionallity of SOA rather than us attempting to mutate existing esb.xml files into add this stuff ?

> 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

       



More information about the jbosstools-issues mailing list