In your solution, a web service client needs to invoke a series of three web services in support of a single transaction. The third web service needs the identity of the original web service client…

Question

Options

• AThe transaction manager accesses an internal table that maintains credentials used to invoke
• BEach web service in the chain does its own authentication so the third web service handles its
• COWSM sets the user in the Java Authentication and Authorization (JAAS) Subject when the first
• DOWSM stores a SAML token from the first web service invocation in a database table, and that

• A
  19% (6)
• B
  3% (1)
• C
  71% (22)
• D
  6% (2)

Explanation

Propagating Identities through a Chain of Web Services A web service may invoke another web service which in turn may invoke yet another web service to complete a single transaction (this pattern is known as "chained web services"). Eachof the services in the chain may be protected. Instead of checking which service is calling which other service, Oracle WSM allows you to check who the original user invoking the chain of Web services is. Oracle WSM policies can be used to propagate the original user's identity across the chained web services. Following successful authentication to the first web service in the chain, Oracle WSM sets the user as a Java Subject used throughout the transaction. When invoking another service, the Oracle WSM client policy picks up the user identity from the Java Subject, generates a SAML token based on the Subject 's information, and inserts the SAML token in the WS-Security header of the request message to be sent to the service provider. This allows all theweb services in a chain to track the identity of the actual user calling a web serviceendpoint instead of having the identity of the prior service in the chain calling the first web service to get that information.

No community discussion yet for this question.