CSOS in Activator

The following figure illustrates how CSOS functionality works in Activator according to the following scenario.

The following illustration shows the flow of CSOS orders.

1. A back-end ordering system generates a purchase order that conforms to CSOS standards.
2. Activator picks up the document. Recognizing it as a CSOS order, Activator places the document in a signing queue. This action suspends the usual processing routine of packaging documents for sending to partners. Only the documents you want are handled in this manner. Other documents are not affected.
3. A CSOS user logs on to Activator user interface to check for CSOS orders awaiting approval.
4. The users views CSOS purchase orders that were delivered and need approval.
5. The user types a password and approves the order. This action results in Activator using the user’s private key to digitally sign the order.
6. The signed order is released for Activator to continue outbound processing to the partner vendor.
7. The partner’s system, upon receiving the signed order, verifies the signature using DEA-issued root and intermediate certificates. The receiver also checks whether the DEA registration number is the same in the order and the root certificate. Orders that fail verification are rejected. For orders that pass verification, an acknowledgement is returned.

Related topics

• Overview of CSOS functionality
• CSOS configuration for sending
• CSOS configuration for receiving
• CSOS configuration for receiving
• CSOS WebTrader
• Import CSOS signing certificate
• CSOS certificate revocation lists
• Identify CSOS purchase orders
• Sign pending orders