Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1169

PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Obsolete
    • Icon: Major Major
    • LATER
    • None
    • integration-platform
    • None

      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.

            bfitzpat_rh Brian Fitzpatrick (Inactive)
            glamperi@redhat.com Gary Lamperillo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: