Web Services Security be Used For a Synchronous Service Operation From PeopleSoft to 3rd Party
To send a synchronous service operation from PeopleSoft to
3rd party using Web Services (WS) Security with encryption and a digital
signature.
Username Token can be a userid with/without password. Userid
can be external userid, which is defined on the Node Definition. It can be
plain / clear-text meaning without being digitally signed and/or
encrypted.
In PT 8.48-8.49, Web Services (WS) Security works with request service operations only.
In PT 8.48-8.49, Web Services (WS) Security works with request service operations only.
Types
of service operation
|
WS
Security
|
Asynchronous one-way
inbound
|
Request
|
Asynchronous one-way
outbound
|
Request
|
Synchronous outbound
|
Request only. The
response returned cannot have WSS applied
|
Synchronous Inbound
|
Request only. The
response sent cannot have WSS applied
|
Asynchronous-
request/response
|
WSS is not applied at
all.
|
WSS can not be applied to response to 3rd party. This is a
limitation of WSS implementation in PeopleTools Release 8.48 and 8.49.
In
PT 8.50+, support to SAML Token is added, and WS Security is implemented for
both request and response.
Type of Service
Operation
|
WS Security
|
Asynchronous one-way
inbound
|
Request
|
Asynchronous one-way
outbound
|
Request
|
Synchronous outbound
|
Request and Response
|
Synchronous inbound
|
Request and Response
|
Asynchronous-
request/response
|
Request and Response
|
Comments
Post a Comment