Configuring Nonrepudiation
This section discusses nonrepudiation configuration tasks on sending and target PeopleSoft systems using PeopleSoft Integration Broker.
If a participating node doesn’t use PeopleSoft Integration Broker, that node is still responsible for managing the appropriate private and public keys, inserting properly formatted signatures in the nonrepudiation service operation it sends, and properly handling signatures in the service operations that it receives.
With both archived and active nonrepudiation service operations, you can regenerate the digest in the Service Operations Monitor to reconfirm that it matches the attached digest.
See Integration Broker Service Operations Monitor: Viewing Nonrepudiation Signatures in XML Format.
Configuring Nonrepudiation on Sending PeopleSoft Systems
This section discusses configuring nonrepudiation on sending systems for asynchronous or synchronous transactions.
Prerequisites for configuring nonrepudiation are discussed elsewhere in this section.
See Prerequisites for Implementing Nonrepudiation.
To configure nonrepudiation for service operations on the source system you must:
-
Select the Non-Repudiation check box on the service operation that will be invoked.
-
Select the Non-Repudiation check box on the remote node definition that represents the target system.
Configuring Nonrepudiation on Target PeopleSoft Systems
You must supply the digital certificates containing the private and public keys required for nonrepudiation transactions.
No additional configuration is required on target PeopleSoft systems to handle nonrepudiated service operations. A nonrepudiated service operation received by a target PeopleSoft system will attempt to validate the service operation regardless if the local node and service operation are set for nonrepudiation.
Saving Nonrepudiated Service Operations
To save nonrepudiation service operations for future reference, you must archive them.
See Integration Broker Service Operations Monitor: Archiving Service Operations.