Describing WS-Security Configuration Options for Outbound Integrations (Username Tokens)

This section discusses:

Recommended WS-Security configurations for outbound integrations.
Supported WS-Security configurations for outbound integrations.
Non-secure WS-Security configurations for outbound integrations.

Recommended WS-Security Configurations for Outbound Integrations (Username Token)

The following table highlights recommended WS-Security configurations on the PeopleSoft system for outbound integrations using Username tokens. Note that the configuration is always performed on the remote node and that the node type is always External.

External User ID and Password	Authentication Type	With SSL Encryption	Results
Both	Username Token with the External User ID option.	Yes	The system uses the external user ID and password to generate the username token. The token is generated in clear text.
Both	Username Token with the following other options: External User ID. Encrypted. Digitally signed.	No	The system uses the external user ID and password to generate the username token. The token is encrypted and digitally signed.
Both	Username Token with the Digitally signed option.	Yes	The system uses the external user ID and password to generate the username token. The token is digitally signed.
External User ID only.	Username Token with the External User ID option.	Yes	The system uses the external user ID to generate the username token. The token is generated in clear text.
External User ID only.	Username Token with the following other options: External User ID. Encrypted. Digitally signed.	No	The system uses the external user ID to generate the username token. The token is encrypted and digitally signed.
External User ID only.	Username Token with the following other options: External User ID. Digitally signed.	No	The system uses the external user ID to generate the username token. The token is digitally signed.

Supported WS-Security Configurations for Outbound Integrations (Username Token)

The following table highlights supported WS-Security configurations on the PeopleSoft system for outbound integrations using Username tokens. Note that the configuration is always performed on the remote node and that the node type is always External.

External User ID and Password	Authentication Type	With SSL Encryption	Results
None.	Username Token option only.	Yes.	The system uses the default user ID defined on the node definition to generate the username token. The token is generated in clear text.
None.	Username Token with the following other options: Encrypted. Digitally signed.	No.	The system uses the default user ID defined on the node definition to generate the username token. The token is encrypted and digitally signed.
None	Username Token with the Digitally Signed option.	No.	The system uses the default user ID defined on the node definition to generate the username token. The token is digitally signed.

External User ID and Password

Authentication Type

With SSL Encryption

Results

None.

Username Token option only.

Yes.

The system uses the default user ID defined on the node definition to generate the username token. The token is generated in clear text.

None.

Username Token with the following other options:

Encrypted.
Digitally signed.

No.

The system uses the default user ID defined on the node definition to generate the username token. The token is encrypted and digitally signed.

None

Username Token with the Digitally Signed option.

No.

The system uses the default user ID defined on the node definition to generate the username token. The token is digitally signed.

Non-Secure WS-Security Configurations for Outbound Integrations (Username Token)

The following table highlights non-secure WS-Security configurations on the PeopleSoft system for outbound integrations using Username tokens. Note that the configuration is always performed on the remote node and that the node type is always External.

WARNING:

The following configurations are not secure! This information is provided to advise you about configurations that can lead to breaches in security. Use the recommended or supported configurations discussed in the previous sections for configuring your system .

External User ID and Password	Authentication Type	With SSL Encryption	Results
Both	Username Token with the External user ID option.	No.	The system uses the external user ID and password to generate the username token. The token is generated in clear text.
None.	Username Token option only.	No.	The system uses the default user ID defined on the node definition to generate the username token. The token is generated in clear text.
Both	Username Token with the following options: External user ID. Encrypted.	No.	The system uses the external user ID and password to generate the username token. The token is encrypted.
None.	Username Token with the following options: External user ID. Encrypted.	No.	The system uses the default user ID and password to generate the username token. The token generated is encrypted.