Use the predefined assertion templates to construct your own policies or clone to create new policies. This chapter describes the predefined assertion templates defined for the current release.
Notes:
The predefined policies and assertion templates distributed with the current release are read only. You must copy the policy or assertion template before modifying it. You also have the option of configuring the attributes in an assertion after you have added it to a policy. For information about managing the assertion templates and adding them to policies, see "Managing Policy Assertion Templates".
If you have modified any of the predefined policies or assertion templates from the previous release (11g), they will be replaced by read only versions in the next release. For more information, see "Overview of Web Services Policy Management".
This chapter contains the following sections:
For a detailed description of the configuration settings in the tables, see "Assertion Template Settings Reference".
For a detailed description of the configuration properties listed in the tables, see "Assertion Template Configuration Properties Reference". For details on how to edit the configuration properties, see "Editing the Configuration Properties in an Assertion Template". For information about overriding policies, see "Overview of Policy Configuration Overrides".
The following sections describe the security assertion templates in more detail.
You can jump to a specific assertion template description using the following links (listed alphabetically):
oracle/http_spnego_token_client_template or oracle/http_spnego_token_service_template
oracle/http_saml20_token_bearer_client_template or oracle/http_saml20_token_bearer_service_template
oracle/wss_http_token_over_ssl_client_template or oracle/wss_http_token_over_ssl_service_template
oracle/wss_http_token_client_template or oracle/wss_http_token_service_template
oracle/wss_saml_token_bearer_over_ssl_client_template or oracle/wss_saml_token_bearer_over_ssl_service_template
oracle/wss_saml20_token_bearer_over_ssl_client_template or oracle/wss_saml20_token_bearer_over_ssl_service_template
oracle/wss_saml_token_over_ssl_client_template or oracle/wss_saml_token_over_ssl_service_template
oracle/wss_saml20_token_over_ssl_client_template or oracle/wss_saml20_token_over_ssl_service_template
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template or oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template
oracle/wss_username_token_over_ssl_client_template or oracle/wss_username_token_over_ssl_service_template
oracle/wss_username_token_client_template or oracle/wss_username_token_service_template
oracle/wss_username_token_over_ssl_client_template or oracle/wss_username_token_over_ssl_service_template
oracle/wss10_message_protection_client_template or oracle/wss10_message_protection_service_template
oracle/wss10_saml_token_client_template or oracle/wss10_saml_token_service_template
oracle/wss10_saml20_token_client_template or oracle/wss10_saml20_token_service_template
oracle/wss10_saml_token_with_message_protection_client_template or oracle/wss10_saml_token_with_message_protection_service_template
oracle/wss10_saml20_token_with_message_protection_client_template or oracle/wss10_saml20_token_with_message_protection_service_template
oracle/wss10_username_token_with_message_protection_client_template or oracle/wss10_username_token_with_message_protection_service_template
oracle/wss10_x509_token_with_message_protection_client_template or oracle/wss10_x509_token_with_message_protection_service_template
oracle/wss11_kerberos_token_client_template or oracle/wss11_kerberos_token_service_template
oracle/wss11_kerberos_token_with_message_protection_client_template or oracle/wss11_kerberos_token_with_message_protection_service_template
oracle/wss11_saml_token_with_message_protection_client_template or oracle/wss11_saml_token_with_message_protection_service_template
oracle/wss11_saml20_token_with_message_protection_client_template or oracle/wss11_saml20_token_with_message_protection_service_template
oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template or oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template
oracle/wss11_sts_issued_saml_with_message_protection_client_template
oracle/wss11_username_token_with_message_protection_client_template or oracle/wss11_username_token_with_message_protection_service_template
oracle/wss11_x509_token_with_message_protection_client_template or oracle/wss11_x509_token_with_message_protection_service_template
Table 19-1 summarizes the assertion templates that enforce authentication only, and indicates whether the token is inserted at the transport layer or SOAP header.
Table 19-1 Authentication Only Assertion Templates
| Client Template | Service Template | Authentication Transport | Authentication SOAP | Authentication REST | Message Protection Transport | Message Protection SOAP |
|---|---|---|---|---|---|---|
|
N/A |
No |
No |
Yes |
No |
No |
|
|
No |
No |
Yes |
Yes |
No |
||
|
No |
No |
Yes |
Yes |
No |
||
|
Yes |
No |
No |
No |
No |
||
|
No |
Yes |
No |
No |
No |
||
|
No |
Yes |
No |
No |
No |
||
|
No |
Yes |
No |
No |
No |
||
|
No |
Yes |
No |
No |
No |
Display Name: Http OAM Service Assertion Template
Category: Security
Type: http-oam-security
The http_oam_token_service_template assertion template verifies that OAM agent has authenticated the user and has established an identity. This policy can be applied to any HTTP-based endpoint.
Table 19-2 lists the settings for the http_oam_token_service_template assertion template.
Table 19-2 http_oam_token_service_template Settings
| Name | Default Value |
|---|---|
|
Authentication Header |
|
|
|
|
|
None |
Table 19-3 lists the default configuration properties for the http_oam_token_service_template assertion template.
Display Name: Http Saml Bearer V2.0 Token Client Assertion Template
Category: Security
Type: http-saml20-bearer-security
The http_saml20_token_bearer_client_template assertion template includes SAML 2,0 tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.
Table 19-4 lists the settings for the http_saml20_token_bearer_client_template assertion template.
Table 19-4 http_saml20_token_bearer_client_template Settings
| Name | Default Value |
|---|---|
|
Authentication Header |
|
|
|
|
|
None |
Table 19-5 lists the configuration properties and the default settings for the http_saml20_token_bearer_client_template assertion template.
Display Name: Http Saml Bearer V2.0 Token Service Assertion Template
Category: Security
Type: http-saml20-bearer-security
The http_saml20_token_bearer_service_template assertion template authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.
The settings for the http_saml20_token_bearer_service_template assertion template are identical to the client version of the assertion template. See Table 19-4 for information about the settings.
Table 19-45 lists the configuration properties and the default settings for the http_saml20_token_bearer_service_template assertion template.
Display Name: SPNEGO Token Client Assertion Template
Category: Security
Type: http-spnego-security
The http_spnego_token_client_template assertion template provides authentication using a Kerberos token and the Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) protocol.
Table 19-7 lists the settings for the http_spnego_token_client_template assertion template.
Table 19-7 http_spnego_token_client_template Settings
| Name | Default Value |
|---|---|
|
Authentication Header |
|
|
|
|
|
None |
Table 19-8 lists the default configuration properties for the http_spnego_token_client_template assertion template.
Display Name: SPNEGO Token Service Assertion Template
Category: Security
Type: http-spnego-security
The http_spnego_token_service_template assertion template provides authentication using a Kerberos token and the SPNEGO protocol.
The settings for the http_spnego_token_service_template assertion template are identical to the client version of the assertion template. See Table 19-7 for information about the settings.
Table 19-9 lists the default configuration properties for the http_spnego_token_service_template assertion template.
Display Name: Wss HTTP Token client Assertion Template
Category: Security
Type: http-security
The wss_http_token_client_template assertion template includes username and password credentials in the HTTP header. You can control whether one-way or two-way authentication is required.
Table 19-10 lists the settings for the wss_http_token_client_template assertion template.
Table 19-10 wss_http_token_client_template Settings
| Name | Default Value |
|---|---|
|
Authentication Header |
|
|
|
|
|
None |
|
|
Transport Layer Security |
|
|
Disabled |
|
|
Disabled |
|
|
Disabled |
Table 19-11 lists the default configuration properties for the wss_http_token_client_template assertion template.
Display Name: Wss HTTP Token service Assertion Template
Category: Security
Type: http-security
The wss_http_token_service_template assertion template uses the credentials in the HTTP header to authenticate users against the Oracle Platform Security Services identity store. You can control whether one-way or two-way authentication is required.
The settings for the wss_http_token_service_template are identical to those for the client version of the assertion template. See Table 19-10 for information about the settings.
Table 19-12 lists the default configuration properties for the wss_http_token_service_template assertion template.
Display Name: Wss Username Token client Assertion Template
Category: Security
Type: wss-username-token
The wss_username_token_client_template assertion template includes authentication with username and password credentials in the WS-Security UsernameToken header. The assertion supports three types of password credentials: plain text, digest, and no password.
Note:
If you do not use a digest password, policies created using this template are not secure. You should use this assertion with plain text or no password in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this assertion, "oracle/wss_username_token_over_ssl_client_template".
To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.
Table 19-13 lists the settings for the wss_username_token_client_template assertion template.
Table 19-13 wss_username_token_client_template Settings
| Name | Default Value |
|---|---|
|
Username Token |
|
|
|
|
|
Disabled |
|
|
Disabled |
Table 19-14 lists the default configuration properties for the wss_username_token_client_template assertion template.
Display Name: Wss Username Token service Assertion Template
Category: Security
Type: wss-username-token
The wss_username_token_service_template assertion template enforces authentication with username and password credentials in the WS-Security UsernameToken SOAP header. The assertion supports three types of password credentials: plain text, digest, and no password.
Note:
If you do not use a digest password, policies created using this template are not secure. You should use this assertion with plain text or no password in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this assertion, "oracle/wss_username_token_over_ssl_service_template".
To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.
The settings for the wss_username_token_service_template are identical to the client version of the assertion template. See Table 19-13 for information about the settings.
Table 19-15 lists the configuration properties and the default settings for the wss_username_token_service_template assertion template.
Display Name: Wss10 SAML Token client Assertion Template
Category: Security
Type: wss10-saml-token
The wss10_saml_token_client_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token is created automatically.
Table 19-16 lists the settings for the wss10_saml_token_client_template assertion template.
Table 19-16 wss10_saml_token_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
unspecified |
Table 19-17 lists the configuration properties and the default settings for the wss10_saml_token_client_template assertion template.
Display Name: Wss10 SAML Token service Assertion Template
Category: Security
Type: wss10-saml-token
The wss10_saml_token_service_template assertion template authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.
The settings for the wss10_saml_token_service_template are identical to the client version of the assertion. See Table 19-16 for information about the settings.
Table 19-18 lists the configuration properties and the default settings for the wss10_saml_token_service_template assertion template.
Display Name: Wss10 SAML V2.0 Token client Assertion Template
Category: Security
Type: wss10-saml-token
The wss10_saml20_token_client_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token is created automatically.
Table 19-19 lists the settings for the wss10_saml20_token_client_template assertion template.
Table 19-19 wss10_saml20_token_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
unspecified |
Table 19-20 lists the configuration properties and the default settings for the wss10_saml20_token_client_template assertion template. For details about the configuration property settings, see "Editing the Configuration Properties in an Assertion Template".
For information about overriding policies, see "Overview of Policy Configuration Overrides".
Display Name: Wss10 SAML V2.0 Token service Assertion Template
Category: Security
Type: wss10-saml-token
The wss10_saml20_token_service_template assertion template authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.
The settings for the wss10_saml20_token_service_template are similar to the client version of the assertion template. See Table 19-19 for information about the settings.
Table 19-21 lists the configuration properties and the default settings for the wss10_saml20_token_service_template assertion template. For details about the configuration property settings, see "Editing the Configuration Properties in an Assertion Template".
For information about overriding policies, see "Overview of Policy Configuration Overrides".
Display Name: Wss11 Kerberos Token client Assertion Template
Category: Security
Type: kerberos-security
The wss11_kerberos_token_client_template assertion template includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
Table 19-22 lists the settings for the wss11_kerberos_token_client_template assertion template.
Table 19-22 wss11_kerberos_token_client_template Settings
| Name | Default Value |
|---|---|
|
Kerberos Token Type |
|
|
|
|
|
Disabled |
Table 19-23 lists the default configuration properties for the wss11_kerberos_token_client_template assertion template.
Display Name: Wss11 Kerberos Token service Assertion Template
Category: Security
Type: kerberos-security
The wss11_kerberos_token_service_template assertion template enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services.
The settings for the wss11_keberos_token_service_template are identical to the client version of the assertion template. See Table 19-22 for information about the settings.
Table 19-24 lists the configuration properties and the default settings for the wss11_kerberos_token_service_template assertion template.
Table 19-25 summarizes the assertion templates that enforce message protection only, and indicates whether the token is inserted at the transport layer or SOAP header.
Table 19-25 Message-Protection Only Assertion Templates
| Client Template | Service Template | Authentication Transport | Authentication SOAP | Message Protection Transport | Message Protection SOAP |
|---|---|---|---|---|---|
|
No |
No |
No |
Yes |
||
|
No |
No |
No |
Yes |
Display Name: Wss10 Message Protection client Assertion Template
Category: Security
Type: wss10-anonymous-with-certificates
The wss10_message_protection_client_template assertion template provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
Table 19-26 lists the settings for the wss10_message_protection_client_template assertion template.
Table 19-26 wss10_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
X509 Token |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation versions 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-27 lists the configuration properties and the default settings for the wss10_message_protection_client_template assertion template.
Display Name: Wss10 Message Protection service Assertion Template
Category: Security
Type: wss10-anonymous-with-certificates
The wss10_message_protection_service_template assertion template provides message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The settings for the wss10_message_protection_service_template are identical to the client version of the assertion template. See Table 19-26 for information about the settings.
Table 19-28 lists the configuration properties and the default settings for the wss10_message_protection_service_template assertion template.
Display Name: Wss11 Message Protection client Assertion Template
Category: Security
Type: wss11-anonymous-with-certificates
The wss11_message_protection_client_template assertion template provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.1 standard.
Table 19-29 lists the settings for the wss11_message_protection_client_template assertion template.
Table 19-29 wss11_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
X509 Token |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-30 lists the configuration properties and the default settings for the wss11_message_protection_client_template assertion template.
Display Name: Wss11 Message Protection service Assertion Template
Category: Security
Type: wss11-anonymous-with-certificates
The wss11_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.1 standard.
The settings for the wss11_message_protection_service_template are identical to the client version of the assertion template. See Table 19-29 for information about the settings.
Table 19-31 lists the configuration properties and the default settings for the wss11_message_protection_service_template assertion template.
Table 19-32 summarizes the assertion templates that enforce both message protection and authentication, and indicates whether the token is inserted at the transport layer or SOAP header.
Table 19-32 Message Protection and Authentication Assertion Templates
Display Name: Wss HTTP Token Over SSL client Assertion Template
Category: Security
Type: http-security
The wss_http_token_over_ssl_client_template assertion template includes credentials in the HTTP header for outbound client requests and authenticates users against the Oracle Platform Security Services identity store. This policy verifies that the transport protocol is HTTPS. Requests over a non-HTTPS transport protocol are refused. This policy can be applied to any HTTP-based client.
Table 19-33 lists the settings for the wss_http_token_over_ssl_client_template assertion template.
Table 19-33 wss_http_token_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
Authentication Header |
|
|
|
|
|
None |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
Table 19-34 lists the configuration properties and the default settings for the wss_http_token_over_ssl_client_template assertion template.
Display Name: Wss HTTP Token Over SSL service Assertion Template
Category: Security
Type: http-security
The wss_http_token_over_ssl_service_template assertion template extracts the credentials in the HTTP header and authenticates users against the Oracle Platform Security Services identity store.
The settings for the wss_http_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-33 for information about the settings.
Table 19-35 lists the configuration properties and the default settings for the wss_http_token_service_template assertion template.
Display Name: Wss SAML Bearer Token client Assertion Template
Category: Security
Type: wss10-saml-token
The wss_saml_token_bearer_client_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.
Table 19-36 lists the settings for the wss_saml_token_bearer_client_template assertion template.
Table 19-36 wss_saml_token_bearer_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
unspecified |
Table 19-41 lists the configuration properties and the default settings for the wss_saml_token_bearer_client_template assertion template.
Display Name: Wss SAML Bearer Token service Assertion Template
Category: Security
Type: wss10-saml-token
The wss_saml_token_bearer_service_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.
Table 19-36 lists the settings for the wss_saml_token_bearer_service_template assertion template.
Table 19-38 wss_saml_token_bearer_service_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
unspecified |
Table 19-41 lists the configuration properties and the default settings for the wss_saml_token_bearer_service_template assertion template.
Display Name: Wss SAML Token (Confirmation method as bearer) Over SSL client Assertion Template
Category: Security
Type: wss-saml-token-bearer-over-ssl
The wss_saml_token_bearer_over_ssl_client template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.
Table 19-40 lists the settings for the wss_saml_token_bearer_over_ssl_client_template assertion template.
Table 19-40 wss_saml_token_bearer_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
unspecified |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
None |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
Table 19-41 lists the configuration properties and the default settings for the wss_saml_token_bearer_over_ssl_client_template assertion template.
Display Name: Wss SAML Token (Confirmation method as bearer) Over SSL service Assertion Template
Category: Security
Type: wss-saml-token-bearer-over-ssl
The wss_saml_token_bearer_over_ssl_service_template assertion template authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.
The settings for the wss_saml_token_bearer_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-40 for information about the settings.
Table 19-42 lists the configuration properties and the default settings for the wss_saml_token_bearer_over_ssl_service_template assertion template.
Display Name: Wss SAML V2.0 Token (Confirmation method as bearer) Over SSL client Assertion Template
Category: Security
Type: wss-saml-token-bearer-over-ssl
The wss_saml20_token_bearer_over_ssl_client template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.
Table 19-43 lists the settings for the wss_saml20_token_bearer_over_ssl_client_template assertion template.
Table 19-43 wss_saml20_token_bearer_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
unspecified |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
None |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
Table 19-44 lists the configuration properties and the default settings for the wss_saml20_token_bearer_over_ssl_client_template assertion template.
Display Name: Wss SAML V2.0 Token (Confirmation method as bearer) Over SSL service Assertion Template
Category: Security
Type: wss-saml-token-bearer-over-ssl
The wss_saml20_token_bearer_over_ssl_service_template assertion template authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.
The settings for the wss_saml20_token_bearer_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-43 for information about the settings.
Table 19-45 lists the configuration properties and the default settings for the wss_saml20_token_bearer_over_ssl_service_template assertion template.
Display Name: Wss SAML Token Over SSL client Assertion Template
Category: Security
Type: wss-saml-token-over-ssl
The wss_saml_token_over_ssl_client_template assertion template enables the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.
Table 19-46 lists the settings for the wss_saml_token_over_ssl_client_template assertion template.
Table 19-46 wss_saml_token_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
|
|
None |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
Table 19-47 lists the configuration properties and the default settings for the wss_saml_token_over_ssl_client_template assertion template.
Display Name: Wss SAML Token Over SSL service Assertion Template
Category: Security
Type: wss-saml-token-over-ssl
The wss_saml_token_over_ssl_service_template enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.
The settings for the wss_saml_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-46 for information about the settings.
Table 19-48 lists the configuration properties and the default settings for the wss_saml_token_over_ssl_service_template assertion template.
Display Name: Wss SAML V2.0 Token Over SSL client Assertion Template
Category: Security
Type: wss-saml-token-over-ssl
The wss_saml20_token_over_ssl_client_template assertion template enables the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.
Table 19-49 lists the settings for the wss_saml20_token_over_ssl_client_template assertion template.
Table 19-49 wss_saml20_token_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
|
|
None |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
Table 19-50 lists the configuration properties and the default settings for the wss_saml20_token_over_ssl_client_template assertion template.
Display Name: Wss SAML V2.0 Token Over SSL service Assertion Template
Category: Security
Type: wss-saml-token-over-ssl
The wss_saml20_token_over_ssl_service_template enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.
The settings for the wss_saml20_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-49 for information about the settings.
Table 19-51 lists the configuration properties and the default settings for the wss_saml20_token_over_ssl_service_template assertion template.
Display Name: Wss Username Token Over SSL client Assertion Template
Category: Security
Type: wss-username-token-over-ssl
The wss_username_token_over_ssl_client_template assertion template includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages. The assertion supports three types of password credentials: plain text, digest, and no password.
To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.
Table 19-52 lists the settings for the wss_username_token_over_ssl_client_template assertion template.
Table 19-52 wss_username_token_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
Username Token |
|
|
|
|
|
Disabled |
|
|
Enabled |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
None |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
Table 19-53 lists the configuration properties and the default settings for the wss_username_token_over_ssl_client_template assertion template.
Display Name: Wss Username Token Over SSL service Assertion Template
Category: Security
Type: wss-username-token-over-ssl
The wss_username_token_over_ssl_service_template assertion template uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users against the Oracle Platform Security Services configured identity store. The assertion supports three types of password credentials: plain text, digest, and no password.
To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.
The settings for the wss_username_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-52 for information about the settings.
Table 19-54 lists the configuration properties and the default settings for the wss_username_token_over_ssl_service_template assertion template.
Display Name: Wss10 SAML Holder-Of-Key Token with Message Protection client Assertion Template
Category: Security
Type: wss10-saml-hok-with-certificates
The wss10_saml_hok_token_with_message_protection_client_template assertion template provides message protection (integrity and confidentiality) and SAML holder of key based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
Table 19-55 lists the settings for the wss10_saml_hok_token_with_message_protection_client_template assertion template.
Table 19-55 wss10_saml_hok_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
X509 Token |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-56 lists the configuration properties and the default settings for the wss10_saml_hok_token_with_message_protection_client_template assertion template.
Display Name: Wss10 SAML Holder-Of-Key Token with Message Protection service Assertion Template
Category: Security
Type: wss10-saml-hok-with-certificates
The wss10_saml_hok_token_with_message_protection_service_template assertion template enforces message-level protection and SAML holder of key based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The settings for the wss10_saml_hok_token_with_message_protection_service_template are identical to those for the client version of the assertion template. See Table 19-55 for information about the settings.
Table 19-57 lists the configuration properties and the default settings for the wss10_saml_hok_token_with_message_protection_service_template assertion template.
Display Name: Wss10 SAML Token with Message Protection client Assertion Template
Category: Security
Type: wss10-saml-with-certificates
The wss10_saml_token_with_message_protection_client_template assertion template provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.
To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.
Table 19-58 lists the settings for the wss10_saml_token_with_message_protection_client_template assertion template.
Table 19-58 wss10_saml_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
X509 Token |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-59 lists the configuration properties and the default settings for the wss10_saml_token_with_message_protection_client_template assertion template.
Table 19-59 wss10_saml_token_with_message_protection_client_template Configuration Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
|
Required |
|
|
|
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
|
Optional |
|
|
Null |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
Display Name: Wss10 SAML Token with Message Protection service Assertion Template
Category: Security
Type: wss10-saml-with-certificates
The wss10_saml_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.
To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.
The settings for the wss10_saml_token_with_message_protection_service_template are identical to those for client version of the assertion template. See Table 19-58 for information about the settings.
Table 19-60 lists the configuration properties and the default settings for the wss10_saml_token_with_message_protection_service_template assertion template.
Display Name: Wss10 SAML V2.0 Token with Message Protection client Assertion Template
Category: Security
Type: wss10-saml-with-certificates
The wss10_saml20_token_with_message_protection_client_template assertion template provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.
To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.
Table 19-61 lists the settings for the wss10_saml20_token_with_message_protection_client_template assertion template.
Table 19-61 wss10_saml20_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
X509 Token |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-62 lists the configuration properties and the default settings for the wss10_saml20_token_with_message_protection_client_template assertion template.
Table 19-62 wss10_saml20_token_with_message_protection_client_template Configuration Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
|
Required |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
|
Optional |
|
|
|
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
Display Name: Wss10 SAML V2.0 Token with Message Protection service Assertion Template
Category: Security
Type: wss10-saml-with-certificates
The wss10_saml20_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.
To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.
The settings for the wss10_saml20_token_with_message_protection_service_template are similar to those of the client version of the assertion template. See Table 19-61 for information about the settings.
Table 19-63 lists the configuration properties and the default settings for the wss10_saml20_token_with_message_protection_service_template assertion template.
Display Name: Wss10 Username Token with Message Protection client Assertion Template
Category: Security
Type: wss10-username-with-certificates
The wss10_username_token_with_message_protection_client_template assertion template provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard. Credentials are included in the WS-Security UsernameToken header in the outbound SOAP message.
The assertion supports three types of password credentials: plain text, digest, and no password.
To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.
Table 19-64 lists the settings for the wss10_username_token_with_message_protection_client_template assertion template.
Table 19-64 wss10_username_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
Username Token |
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
X509 Token |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-65 lists the configuration properties and the default settings for the wss10_username_token_with_message_protection_client_template assertion template.
Display Name: Wss10 Username Token with Message Protection service Assertion Template
Category: Security
Type: wss10-username-with-certificates
The wss10_username_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The assertion supports three types of password credentials: plain text, digest, and no password.
To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.
The settings for the wss10_username_token_with_message_protection_service_template assertion template are identical to the client version of the assertion template. See Table 19-64 for information about the settings.
Table 19-66 lists the configuration properties and the default settings for the wss10_username_token_with_message_protection_service_template assertion template.
Display Name: Wss10 X509 Token with Message Protection client Assertion Template
Category: Security
Type: wss10-mutual-auth-with-certificates
The wss10_x509_token_with_message_protection_client template assertion template provides message protection (integrity and confidentiality) and certificate credential population for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
Table 19-67 lists the settings for the wss10_x509_token_with_message_protection_client template assertion template.
Table 19-67 wss10_x509_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
X509 Token |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-68 lists the configuration properties and the default settings for the wss10_x509_token_with_message_protection_client_template assertion template.
Display Name: Wss10 X509 Token with Message Protection service Assertion Template
Category: Security
Type: wss10-mutual-auth-with-certificates
The wss10_x509_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The settings for the wss10_x509_token_with_message_protection_service_template assertion template are identical to the client version of the assertion template. See Table 19-67 for information about the settings.
Table 19-69 lists the configuration properties and the default settings for the wss10_x509_token_with_message_protection_service_template assertion template.
Display Name: Wss11 Kerberos Token Over SSL Client Assertion Template
Category: Security
Type: wss11-kerberos-over-ssl-security
The wss11_kerberos_token_over_ssl_client_template assertion template includes a Kerberos token in the WS-Security SOAP header in accordance with the WS-Security Kerberos Token Profile v1.1 standard. The Kerberos token is advertised as an EndorsingSupportingToken, and is used only for authentication and for signing the timestamp. Message protection is provided by SSL.
Table 19-70 lists the settings for the wss11_kerberos_token_over_ssl_client_template assertion template.
Table 19-70 wss11_kerberos_token_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
Kerberos Token Type |
|
|
|
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
Table 19-71 lists the configuration properties and the default settings for the wss11_kerberos_token_over_ssl_client_template assertion template.
Display Name: Wss11 Kerberos Token Over SSL Service Assertion Template
Category: Security
Type: wss11-kerberos-over-ssl-security
The wss11_kerberos_token_service_template assertion template enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services. The Kerberos token is advertised as an EndorsingSupportingToken, and is used only for authentication and for signing the timestamp. Message protection is provided by SSL.
The settings for the wss11_kerberos_token_over_ssl_service_template are identical to the client version of the assertion template. See Table 19-70 for information about the settings.
Table 19-72 lists the configuration properties and the default settings for the wss11_kerberos_token_over_ssl_service_template assertion template.
Display Name: Wss11 Kerberos Token with message protection client Assertion Template
Category: Security
Type: kerberos-security
The wss11_kerberos_token_with_message_protection_client_template assertion template includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
Table 19-73 lists the settings for the wss11_kerberos_token_with_message_protection_client_template assertion template.
Table 19-73 wss11_kerberos_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
Kerberos Token Type |
|
|
|
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-74 lists the configuration properties and the default settings for the wss11_kerberos_token_with_message_protection_client_template assertion template.
Display Name: Wss11 Kerberos Token service with message protection Assertion Template
Category: Security
Type: kerberos-security
The wss11_kerberos_token_with_message_protection_service_template assertion template enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services.
The settings for the wss11_keberos_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-73 for information about the settings.
Table 19-75 lists the configuration properties and the default settings for the wss11_kerberos_token_with_message_protection_service_template assertion template.
Display Name: Wss11 SAML Token with Message Protection client Assertion Template
Category: Security
Type: wss11-saml-with-certificates
The wss11_saml_token_with_message_protection_client_template assertion template enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests in accordance with WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.
Table 19-76 lists the settings for the wss11_saml_token_with_message_protection_client_template assertion template.
Table 19-76 wss11_saml_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
X509 Token |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-77 lists the configuration properties and the default settings for the wss11_saml_token_with_message_protection_client_template assertion template.
Table 19-77 wss11_saml_token_with_message_protection_client_template Configuration Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
|
Optional |
|
|
|
Constant |
|
|
|
Required |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
Display Name: Wss11 SAML Token with Message Protection service Assertion Template
Category: Security
Type: wss11-saml-with-certificates
The wss11_saml_token_with_message_protection_service_template assertion template enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.
The settings for the wss11_saml_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-76 for information about the settings.
Table 19-78 lists the configuration properties and the default settings for the wss11_saml_token__with_message_protection_service_template assertion template.
Display Name: Wss11 SAML V2.0 Token with Message Protection client Assertion Template
Category: Security
Type: wss11-saml-with-certificates
The wss11_saml20_token_with_message_protection_client_template assertion template enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests in accordance with WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.
Table 19-79 lists the settings for the wss11_saml20_token_with_message_protection_client_template assertion template.
Table 19-79 wss11_saml20_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
SAML Token Type |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
unspecified |
|
|
X509 Token |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-80 lists the configuration properties and the default settings for the wss11_saml20_token_with_message_protection_client_template assertion template.
Table 19-80 wss11_saml20_token_with_message_protection_client_template Configuration Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
|
Optional |
|
|
|
Constant |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Required |
|
|
|
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
|
Optional |
Display Name: Wss11 SAML V2.0 Token with Message Protection service Assertion Template
Category: Security
Type: wss11-saml-with-certificates
The wss11_saml20_token_with_message_protection_service_template assertion template enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.
The settings for the wss11_saml_token_with_message_protection_service_template are similar to the client version of the assertion template. See Table 19-78 for information about the settings.
Table 19-81 lists the configuration properties and the default settings for the wss11_saml20_token__with_message_protection_service_template assertion template.
Display Name: Wss11 Username Token with Message Protection client Assertion Template
Category: Security
Type: wss11-username-with-certificates
The ws11_username_token_with_message_protection_client_template assertion template includes authentication and message protection in accordance with the WS-Security v1.1 standard.
The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature.
To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.
Table 19-82 lists the settings for the wss11_username_token_with_message_protection_client_template assertion template.
Table 19-82 wss11_username_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
Username Token |
|
|
|
|
|
Disabled |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
X509 Token |
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-83 lists the configuration properties and the default settings for the wss11_username_token_with_message_protection_client_template assertion template.
Display Name: Wss11 Username Token with Message Protection service Assertion Template
Category: Security
Type: wss11-username-with-certificates
The ws11_username_token_with_message_protection_service_template assertion template enforces authentication and message protection in accordance with the WS-Security v1.1 standard.
The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature. To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.
The settings for the wss11_username_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-82 for information about the settings.
Table 19-84 lists the configuration properties and the default settings for the wss11_username_token_with_message_protection_service_template assertion template.
Display Name: Wss11 X509 Token with Message Protection client Assertion Template
Category: Security
Type: wss11-mutual-auth-with-certificates
The wss11_x509_token_with_message_protection_client_template assertion template provides message protection (integrity and confidentiality) and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard. Credentials are included in the WS-Security binary security token of the SOAP message.
Table 19-85 lists the settings for the wss11_x509_token_with_message_protection_client_template assertion template.
Table 19-85 wss11_x509_token_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
X509 Token |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
|
|
N/A |
|
|
N/A |
|
|
N/A |
Table 19-86 lists the configuration properties and the default settings for the wss11_x509_token_with_message_protection_client_template assertion template.
Display Name: Wss11 X509 Token with Message Protection service Assertion Template
Category: Security
Type: wss11-mutual-auth-with-certificates
The wss11_x509_token_with_message_protection_service_template assertion template enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. The certificate is extracted from the WS-Security binary security token header, and the credentials in the certificate are validated against the Oracle Platform Security Services identity store.
The settings for the wss11_x509_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-85 for information about the settings.
Table 19-87 lists the configuration properties and the default settings for the wss11_x509_token_with_message_protection_service_template assertion template.
Table 19-88 summarizes the assertion templates that are used for OES integration.
Table 19-88 OES Integration Templates
| Service Template | Description |
|---|---|
|
Reserved for future use. |
|
|
Reserved for future use. |
|
|
Reserved for future use. |
Reserved for future use.
Reserved for future use.
Reserved for future use.
Table 19-89 summarizes the assertion templates that are used for PII security.
Table 19-90 summarizes the WS-Trust assertion templates.
In this release, you can use Fusion Middleware Control to directly edit the assertion template text, but the Settings and Configuration pages are not available.
Table 19-90 WS-Trust Assertion Templates
| Name | Description |
|---|---|
|
STS configuration information assertion template that is used to invoke STS for token exchange. |
|
|
STS configuration information assertion template that is used to invoke STS for token exchange. |
|
|
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template |
SOAP binding-level client assertion template for issued token SAML authentication (confirmation method bearer), with SSL message protection. |
|
oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template |
SOAP binding-level service assertion template for issued token SAML authentication (confirmation method bearer), with SSL message protection. |
|
oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template |
WS-Security 1.1 issued token SAML HOK token with certificates client assertion template. Provides authentication and message protection using Basic128. |
|
oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template |
WS-Security 1.1 issued token SAML HOK token with certificates service assertion template. Provides authentication and message protection using Basic128. |
|
oracle/wss11_sts_issued_saml_with_message_protection_client_template |
WS-Security 1.1 issued token SAML sender voucher with certificates. Provides authentication and message protection using Basic128. |
Display Name: Trust Configuration Client Assertion Template
Category: Security
Type: sts-trust-config
STS Configuration information, provided on the client side, that is used to invoke STS for token exchange.
Table 19-91 lists the settings for the oracle/sts_trust_config_client_template assertion template.
Table 19-91 oracle/sts_trust_config_client_template Settings
| Name | Default Value |
|---|---|
|
STS Configuration |
|
|
Yes |
|
|
WSDL |
http://host:port/sts?wsdl |
|
Blank |
|
|
Service |
Blank |
|
Port |
Blank |
|
target-namespace#wsdl.endpoint(service-name/port-name) |
|
|
Blank |
|
|
Client Policy URI |
Show All Client Policies |
|
sts-csf-key |
Table 19-92 lists the configuration properties and the default settings for the oracle/sts_trust_config_client_template assertion template.
Display Name: Trust Configuration Service Assertion Template
Category: Security
Type: sts-trust-config
Minimal STS Configuration information, provided on the service side, that is used to obtain all other STS information and invoke STS for token exchange.
Table 19-93 lists the settings for the oracle/sts_trust_config_service_template assertion template.
Table 19-93 oracle/sts_trust_config_service_template Settings
| Name | Default Value |
|---|---|
|
STS Configuration |
|
|
Yes |
|
|
WSDL |
|
|
|
Table 19-94 lists the configuration properties and the default settings for the oracle/sts_trust_config_service_template assertion template.
Display Name: Wss Issued Saml Bearer Token with Message Protection Client Assertion Template
Category: Security
Type: wss-sts-issued-token-over-ssl
SOAP binding level policy for Issued Token SAML authentication (confirmation method as bearer) with SSL Message Protection.
Table 19-95 lists the settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template assertion template.
Table 19-95 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template Settings
| Name | Default Value |
|---|---|
|
Issued Token |
|
|
|
|
|
|
|
|
Blank |
|
|
Disabled |
|
|
Transport Layer Security |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
|
|
None |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Disabled |
|
|
Enabled |
Table 19-96 lists the configuration properties and the default settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template assertion template.
Table 19-96 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Required |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
Display Name: Wss Issued Saml Bearer Token with Message Protection Service Assertion Template
Category: Security
Type: wss-sts-issued-token-over-ssl
SOAP binding level policy for Issued Token SAML authentication (confirmation method as bearer) With SSL Message Protection.
Table 19-95 lists the settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template assertion template.
Table 19-97 lists the configuration properties and the default settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template assertion template.
Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Client Assertion Template
Category: Security
Type: wss11-sts-issued-token-with-certificates
WS-Security 1.1 Issued Token SAML HOK with Certificates. Provides Authenticates and Message Protection using Basic128.
Table 19-98 lists the settings for the wss11_sts_issued_saml_hok_with_message_protection_client_template assertion template.
Table 19-98 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
Issued Token |
|
|
|
|
|
|
|
|
|
|
|
Disabled |
|
|
X509 Token |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
Table 19-99 lists the configuration properties and the default settings for the wss11_sts_issued_saml_hok_with_message_protection_client_template assertion template.
Table 19-99 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Required |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
|
Required |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Service Assertion Template
Category: Security
Type: wss11-sts-issued-token-with-certificates
WS-Security 1.1 Issued Token SAML HOK with Certificates. Provides Authenticates and Message Protection using Basic128.
Table 19-98 lists the settings for the wss11_sts_issued_saml_hok_with_message_protection_service_template assertion template.
Table 19-100 lists the configuration properties and the default settings for the wss11_sts_issued_saml_hok_with_message_protection_service_template assertion template.
Display Name: Wss11 Issued Token Saml Sender Voucher with Message Protection Client Assertion Template
Category: Security
Type: wss11-sts-issued-token-with-certificates
WS-Security 1.1 Issued Token SAML Sender Voucher with Certificates. Provides Authenticates and Message Protection using Basic128.
Table 19-101 lists the settings for the wss11_sts_issued_saml_with_message_protection_client_template assertion template.
Table 19-101 wss11_sts_issued_saml_with_message_protection_client_template Settings
| Name | Default Value |
|---|---|
|
Issued Token |
|
|
|
|
|
Blank |
|
|
|
|
|
Disabled |
|
|
X509 Token |
|
|
|
|
|
|
|
|
Enabled |
|
|
Disabled |
|
|
Disabled |
|
|
Secure Conversation |
|
|
Disabled |
|
|
1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well. |
|
|
Disabled |
|
|
Enabled |
|
|
Enabled |
|
|
Enabled |
|
|
Inherit from Application Setting |
|
|
Message Security |
|
|
|
|
|
Enabled |
|
|
Enabled |
|
|
Disabled |
Table 19-102 lists the configuration properties and the default settings for the wss11_sts_issued_saml_with_message_protection_client_template assertion template.
Table 19-102 oracle/wss11_sts_issued_saml_with_message_protection_client_template Properties
| Name | Default Value | Type |
|---|---|---|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Required |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
None |
Optional |
|
|
|
Optional |
|
|
None |
Optional |
Table 19-103 summarizes assertion templates that are used for authorization. Each authorization assertion template must follow an authentication assertion template.
Table 19-103 Authorization Assertion Templates
| Service Template | Description |
|---|---|
|
Provides simple role-based authorization for the request based on the authenticated subject at the SOAP binding level. |
|
|
Provides simple permission-based authorization for the request based on the authenticated subject at the SOAP binding level. |
|
|
Provides simple role-based authorization for the request based on the authenticated subject at the SOA component level. |
|
|
Provides simple permission-based authorization for the request based on the authenticated subject at the SOA component level. |
Display Name: Binding Authorization Assertion Template
Category: Security
Type: binding-authorization
The binding_authorization_template assertion template provides simple role-based authorization for the request based on the authenticated subject at the SOAP binding level. It should follow an authentication assertion template.
Table 19-104 lists the settings for the binding_authorization_template assertion template.
Table 19-104 binding_authorization_template Settings
| Name | Default Value |
|---|---|
|
Authorization Permission |
|
|
Permissions—Action Match |
Blank |
|
Permissions—Constraint Match |
Blank |
|
Permissions—Resource Match |
Blank |
|
Not Set |
Table 19-105 lists the configuration properties and the default settings for the binding_authorization_template assertion template.
Display Name: Binding Permission Based Authorization Assertion Template
Category: Security
Type: binding-permission-authorization
The binding_permission_authorization_template assertion provides simple permission-based authorization for the request based on the authenticated subject at the SOAP binding level. It should follow an authentication assertion.
Table 19-106 lists the settings for the binding_permission_authorization_template assertion template.
Table 19-106 binding_permission_authorization_template Settings
| Name | Default Value |
|---|---|
|
Authorization Permission |
|
|
Permissions—Action Match |
* |
|
Permissions—Constraint Match |
Blank |
|
Permissions—Resource Match |
* |
|
Blank |
Table 19-107 lists the configuration properties for the binding_permission_authorization_template assertion template.
Display Name: Component Authorization Assertion Template
Category: Security
Type: sca-component-authorization
The component_authorization_template assertion provides simple role-based authorization for the request based on the authenticated subject at the SOA component level. It should follow an authentication assertion.
Table 19-108 lists the settings for the component_authorization_template assertion template.
Table 19-108 component_authorization_template Settings
| Name | Default Value |
|---|---|
|
Authorization Permission |
|
|
Permissions—Action Match |
Blank |
|
Permissions—Constraint Match |
Blank |
|
Permissions—Resource Match |
Blank |
|
Not Set |
Table 19-109 lists the configuration properties for the component_authorization_template assertion template.
Display Name: Component Permission Based Authorization Assertion Template
Category: Security
Type: sca-component-permission-authorization
The component_permission_authorization_template assertion template provides simple permission-based authorization for the request based on the authenticated subject at the SOA component level. It should follow an authentication assertion.
Note:
You should be careful when using permission-based policies with EJBs as the security permissions specified in system-jazn-data.xml will be relaxed beyond a single invocation of the service operation.
Table 19-110 lists the settings for the component_permission_authorization_template assertion template.
Table 19-110 component_permission_authorization_template Settings
| Name | Default Value |
|---|---|
|
Authorization Permission |
|
|
Permissions—Action Match |
* |
|
Permissions—Constraint Match |
N/A |
|
Permissions—Resource Match |
* |
|
N/A |
Table 19-111 lists the configuration properties for the component_permission_authorization_template assertion template.
Table 19-112 lists the algorithm suites that are supported for message protection. The algorithm suites enable you to control the cryptographic characteristics of the algorithms that are used when securing messages.
Table 19-112 Supported Algorithm Suites
| Algorithm Suite | Digest | Encryption | Symmetric Key Wrap | Asymmetric Key Wrap | Encrypted Key Derivation | Signature Key Derivation | Minimum Signature Key Length |
|---|---|---|---|---|---|---|---|
|
Basic256 |
Sha1 |
Aes256 |
KwAes256 |
KwRsaOaep |
PSha1L256 |
PSha1L192 |
256 |
|
Basic192 |
Sha1 |
Aes192 |
KwAes192 |
KwRsaOaep |
PSha1L192 |
PSha1L192 |
192 |
|
Basic128 |
Sha1 |
Aes128 |
KwAes128 |
KwRsaOaep |
PSha1L128 |
PSha1L128 |
128 |
|
TripleDes |
Sha1 |
TripleDes |
KwTripleDes |
KwRsaOaep |
PSha1L192 |
PSha1L192 |
192 |
|
Basic256Rsa15 |
Sha1 |
Aes256 |
KwAes256 |
KwRsa15 |
PSha1L256 |
PSha1L192 |
256 |
|
Basic192Rsa15 |
Sha1 |
Aes192 |
KwAes192 |
KwRsa15 |
PSha1L192 |
PSha1L192 |
192 |
|
Basic128Rsa15 |
Sha1 |
Aes128 |
KwAes128 |
KwRsa15 |
PSha1L128 |
PSha1L128 |
128 |
|
TripleDesRsa15 |
Sha1 |
TripleDes |
KwTripleDes |
KwRsa15 |
PSha1L192 |
PSha1L192 |
192 |
|
Basic256Sha256 |
Sha256 |
Aes256 |
KwAes256 |
KwRsaOaep |
PSha1L256 |
PSha1L192 |
256 |
|
Basic192Sha256 |
Sha256 |
Aes192 |
KwAes192 |
KwRsaOaep |
PSha1L192 |
PSha1L192 |
192 |
|
Basic128Sha256 |
Sha256 |
Aes128 |
KwAes128 |
KwRsaOaep |
PSha1L128 |
PSha1L128 |
128 |
|
TripleDesSha256 |
Sha256 |
TripleDes |
KwTripleDes |
KwRsaOaep |
PSha1L192 |
PSha1L192 |
192 |
|
Basic256Sha256Rsa15 |
Sha256 |
Aes256 |
KwAes256 |
KwRsa15 |
PSha1L256 |
PSha1L192 |
256 |
|
Basic192Sha256Rsa15 |
Sha256 |
Aes192 |
KwAes192 |
KwRsa15 |
PSha1L192 |
PSha1L192 |
192 |
|
Basic128Sha256Rsa15 |
Sha256 |
Aes128 |
KwAes128 |
KwRsa15 |
PSha1L128 |
PSha1L128 |
128 |
|
TripleDesSha256Rsa15 |
Sha256 |
TripleDes |
KwTripleDes |
KwRsa15 |
PSha1L192 |
PSha1L192 |
192 |
Table 19-113 lists the settings for the Request, Response, and Fault messages. You configure these settings for message signing and encryption.
Table 19-114 summarizes the management assertion templates.
Table 19-114 Management Assertion Templates
| Name | Description |
|---|---|
|
Provides a logging assertion template that can be attached to any binding or component. |
Display Name: Security Log Assertion Template
Category: Security
Type: Logging
The security_log_template assertion template provides a logging assertion template that can be attached to any binding or component.
Note:
It is recommended that the logging assertion be used for debugging and auditing purposes only.
Table 19-115 lists the settings for the security_log_template assertion template.
Table 19-116 lists the configuration properties for the security_log_template assertion template.
The following sections summarize the settings that can be set for the predefined assertion templates; settings are listed alphabetically.
Note:
Not all settings apply to all assertion templates.
Action or Web service operation for which authorization checks are performed. This value can be a comma-separated list of values. This field accepts wildcards.For example, validate,amountAvailable.
Algorithm suite used for message protection. See "Supported Algorithm Suites".
Name of the authentication header.
Authentication mechanism.
Valid values include:
basic—Client authenticates itself by transmitting the username and password.
Note: It is recommended that you configure SSL when using basic authentication. For more information, see "Configuring Keystores for SSL".
cert—Not supported in this release. Client authenticates itself by transmitting a certificate.
custom—Not supported in this release. Custom authentication mechanism.
digest— Not supported in this release. Client authenticates itself by transmitting an encrypted password through the use of an MD5 digest.
oam—Client authenticates itself using OAM agent.
saml20-bearer—Client authenticates itself using SAML 2.0 Bearer token.
spnego—Client authenticates itself using Kerberos SPNEGO.
Note: This field is available if Include Entire Body is disabled.
Sign or encrypt the specified body elements. This field is applicable if the Include Body field is disabled.
To add a body element:
Click Add.
Enter the namespace URI.
Enter the local name for the body element.
Click OK.
To edit a body element:
Select the bpdu element that you want to edit in the Body Elements list.
Click Edit.
Modify the values, as required.
Click OK.
To delete a body element:
Select the body element that you want to delete in the Body Elements list.
Click Delete.
When prompted to confirm, click OK.
A Secure Conversation policy has actually two policies: inner and outer. The Bootstrap Message Security control exposes the inner and outer policies. The bootstrap (inner) policy is used to obtain the token and establish the handshake between the client and the Web service. The outer policy is used for application messages when making requests with the token.
See "Using Basic Mode Versus Advanced Mode" in Understanding Oracle Web Services Manager for more information.
This is used as key material for the requested proof token in Secure Conversation.
The client policy URI that will be used by the client to communicate with the STS. The policy you choose depends on the authentication requirements of the STS, as identified in its WSDL.
Flag that specifies whether to send a signature confirmation back to the client.
Confirmation type. The only valid value is:
sender-vouches—Uses the Sender Vouches SAML token for authentication.
Expression that represents the constraints against which authorization checks are performed. The constraints expression is specified using the following two messageContext properties:
messageContext.authenticationMethod—Determines the authentication method used to authenticate the user. Valid value is SAML_SV.
messageContext.requestOrigin—Determines whether the request originated from an internal or external network. This property is valid only when using Oracle HTTP Server and the Oracle HTTP server administrator has added a custom VIRTUAL_HOST_TYPE header to the request.
The constraint pattern properties and their values are case sensitive.
The constraint expression uses the following standard supported operators: ==, !=, &&, || and !.
Flag that specifies whether a time stamp for the creation of the username token is required.
Note: If Password Type is set to digest, then this attribute must be set to true. Otherwise, the policy to which it is attached will not validate.
Flag that specifies whether derived keys should be used.
For the preconfigured WS-SC policies, Secure Conversation is enabled by default. For all of the other policies, Secure Conversation is disabled by default.
Flag that specifies whether to encrypt the signature.
Mechanism used when encrypting the request.
Valid values for wss10_message_protection_client_template and wss10_saml_token_with_message_protection_client_template:
direct—X.509 Token is included in the request.
ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.
issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.
Valid values for wss11_message_protection_client_template, wss11_saml_token_with_message_protection_client_template, wss11_saml20_token_with_message_protection_client_template, wss11_username_token_with_message_protection_client_template, wss11_x509_token_with_message_protection_client_template, wss11_username_token_with_message_protection_client_template:
direct—X.509 Token is included in the request.
ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.
issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.
thumbprint—Fingerprint (SHA1 hash) of the contents of the certificate. Provides a method to store certificates that is low overhead.
See Table 19-113.
Sign or encrypt the specified SOAP header elements.
To add a header element:
Click Add.
Enter the namespace URI.
Enter the local name for the header element.
Click OK.
To edit a header element:
Select the header element that you want to edit in the Header Elements list.
Click Edit.
Modify the values, as required.
Click OK.
To delete a header element:
Select the header element that you want to delete in the Header Elements list.
Click Delete.
When prompted to confirm, click OK.
Sign or encrypt the entire body of the SOAP message.
If false, you can add specific body elements using the Body Elements section.
Sign or encrypt SOAP attachments with MIME headers.
Note: This field is enabled and applicable if Include SwA Attachment is enabled. It is not applicable to MTOM attachments.
Sign or encrypt SOAP messages with attachments.
Note: This field is not applicable to MTOM attachments.
Flag that specifies whether to include a timestamp. A timestamp can be used to prevent replay attacks by identifying an expiration time after which the message is no longer valid.
Flag that specifies whether the SAML token is encrypted.
Flag that specifies whether the SAML token is signed.
Type of Kerberos token. The only valid value is: gss-apreq-v5 (Kerberos Version 5 GSS-API).
Key type. The only valid value is: bearer.
The alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.
Flag that specifies whether two-way authentication is required.
Valid values include:
Enabled—The service must authenticate itself to the client, and the client must authenticate itself to the service.
Disabled—One-way authentication is required. The service must authenticate itself to the client, but the client is not required to authenticate itself to the service.
Specifies the type of format to be used for the name identifier.
Specify one of the following values:
unspecified
emailAddress
X509SubjectName
WindowsDomainQualifiedName
The following assertion templates have the additional value: kerberos:
wss10_saml20_token_client_template, wss_saml20_token_bearer_over_ssl_client_template, wss10_saml20_token_with_message_protection_client_template, wss11_saml20_token_with_message_protection_client_template
Name Identifier Format is applicable only when subject.precedence is set to false. If subject.precedence is false, the user name to create the SAML assertion is obtained from the csf-key property or the username property (see "Configure the Username for the SAML Assertion"). The format of the user name must be the same as the format set in Name Identifier Format.
If subject.precedence is true, the user name to create the SAML assertion is obtained from the Subject. In this case, the Name Identifier Format is always "unspecified" and this cannot be changed by setting Name Identifier Format.
Flag that specifies whether a nonce must be included with the username to prevent replay attacks.
Note: If Password Type is set to digest, then this attribute must be set to true. Otherwise, the policy to which it is attached will not validate.
Type of password required.
Valid values are:
none—No password.
plaintext—Password in clear text.
digest— Client authenticates itself by transmitting an encrypted password through the use of an MD5 digest.
If you specify a password type of None, you do not need to include a password in the key.
Note:
If you do not use a digest password, policies created using this template are not secure; plaintext transmits the password in clear text. You should use this assertion without a digest password in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this assertion, "oracle/wss_username_token_over_ssl_client_template".
Role- and permission-based polices use the guard element (see "orawsp:guard") to define resource, action, and constraint match values. These values allow the assertion execution only if the result of the guard is true. If the accessed resource name and action match, only then is the assertion allowed to execute.
By default, resource name and action use the wildcard asterisk "*" and everything is allowed.
Class used for the permission-based checking. For example, oracle.wsm.security.WSFuncPermission.
You have the option to change the permission_class configuration property for the policy, which identifies the permission class as per JAAS standards. The permission class must be available in the application or server classpath.
The custom permission class must extend the abstract Permission class and implement the Serializable interface. See the Javadoc at http://docs.oracle.com/javase/7/docs/api/java/security/Permission.html.
The default is oracle.wsm.security.WSFunctionPermission.
The endpoint of the STS Web service.For a WSDL 2.0 STS, the format is specified as target-namespace#wsdl.endpoint(service-name/port-name). For example, http://samples.otn.com.LoanFlow#wsdl.endpoint(LoanFlowService/LoanFlowPort). For a WSDL 1.1 STS, the format is specified as targetnamespace#wsdl11.endpoint(servicename/portname). For example, http://samples.otn.com.LoanFlow#wsdl11.endpoint(LoanFlowService/LoanFlowPort).
The actual endpoint URI of the STS port. For example. http://host:port/context-root/service1.
You can enable the re-authenticate control only for SAML sender vouches policies when the propagate.identity.context configuration attribute is set to True, as described in "When to Use Re-Authentication" in Understanding Oracle Web Services Manager.
Mechanism used when encrypting the receipt. Valid values are the same as for Sign Key Reference Mechanism above.
Mechanism used when signing the receipt. Valid values are the same as for "Sign Key Reference Mechanism".
Requirements for logging request messages.
The valid values are:
all—Log the entire SOAP message.
header—Log SOAP header information only.
soap_body—Log SOAP body information only.
soap_envelope—Log SOAP envelope information only.
See Table 19-113.
Optional element. A comma-separated list of XPaths for the request. Default value is blank.
Optional element. A comma-separated list of namespaces for the request, where each namespace has a prefix and URI separated by the equals sign. Default value is blank.
Optional element in the RST. If present, OWSM sends the endpoint address of the Web service for which the token is being requested. The default behavior is to always send the appliesTo element in the message from the client to the STS.
If a symmetric proof key is required by the Web service's security policy, the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.
Indicates whether external reference to the token is required.
Indicates whether internal reference to the token is required.
If a symmetric proof key is required by the Web service's security policy, the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.
Name of the resource for which authorization checks are performed. This field accepts wildcards.For example, if the namespace of the Web service is http://project11 and the service name is CreditValidation, the resource name is http://project11/CreditValidation.
Requirements for logging response messages. The valid values are the same as for Request above.
See Table 19-113.
Optional element. A comma-separated list of namespaces, where each namespace has a prefix and URI separated by the equals sign. Default value is blank.
Optional element. A comma-separated list of XPaths for the response. Default value is blank.
Specifies the roles that are authorized.
The valid values are:
Permit All—Permit users with any roles.
Deny All—Deny all users with roles.
Selected Roles—Permit selected roles.
To add roles:
Click Add.
To add roles, click the checkbox next to each role you want to add in the Roles Available column and click Move. To add all roles, click Move All.
To remove roles, click the checkbox next to each role you want to remove in the Roles Selected to Add column, and click Remove. To remove all roles, click Remove All.
To search for roles, enter a search string in the Role Name search box and click the go arrow. The Roles Available column is updated to include only those roles that match the search string.
Click OK.
To delete roles:
Select the role that you want to delete in the Selected Roles list.
Click Delete.
This is used as key material for the requested proof token for Secure Conversation.
Mechanism used when signing the request.
Valid values include:
direct—X.509 Token is included in the request.
ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.
issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.
thumbprint—Fingerprint (SHA1 hash) of the contents of the certificate. Provides a method to store certificates that is low overhead. This property is valid only for the following templates: wss11_saml_token_with_message_protection_client_template, wss11_saml20_token_with_message_protection_client_template, wss11_x509_token_with_message_protection_client_template, wss11_sts_issued_saml_with_message_protection_client_template, oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template.
Flag that specifies whether the request is signed and then encrypted.
SAML token type. The only valid value is: 1.1.
Flag that specifies whether Secure Socket Layer (SSL), otherwise known as Transport Layer Security (TLS), is enabled.
Flag that specifies whether to include a timestamp. A timestamp can be used to prevent replay attacks by identifying an expiration time after which the message is no longer valid.
Flag that specifies whether two-way authentication is required.
Valid values include:
Enabled—The service must authenticate itself to the client, and the client must authenticate itself to the service.
Disabled—One-way authentication is required. The service must authenticate itself to the client, but the client is not required to authenticate itself to the service.
SAML or Secure Conversation version.
WS-Trust version.
Flag that specifies whether derived keys should be used.
Flag that specifies whether X509PKIPathV1 tokens should be processed and propagated.
The actual endpoint URI of the WSDL.
The following sections summarize the configuration properties that can be set for the predefined assertion templates; settings are listed alphabetically.
Note:
Not all configuration properties apply to all assertion templates.
The key derivation algorithm, which should be PBKDF2.
The application name defined in OES. Value can be static or dynamic that uses ${} notation.
The mapping attribute used to represent the attesting entity. Only the DN is currently supported. This attribute is applicable only to sender vouches and then only to message protection use cases. It is not applicable to SAML over SSL policies.
Client's principal name as generated using the ktpass command and mapped to the username for which the kerberos token should be generated. Use the following format: <username>@<REALM NAME>.
Note: keytab.location and caller.principal.name are required for propagating client identity for Java EE applications.
Flag that specifies whether Credential Delegation with Forwarded TGT is supported. For more information, see "Configuring Credential Delegation". This value is false by default.
Credential Store Key that maps to a username and password in the OPSS identity store. For information about how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".
The data encryption algorithm. It should be in the form algorithm/mode/padding.
Optional property. Action that will be used during real authorization. Value can be static or dynamic that uses ${} notation.
Property used by the client to ignore the timestamp in the SOAP security header when it receives the response from the service. The default behavior is to NOT ignore the timestamp (the default value of this property is false). If set to true, then the timestamp is not required in the response message; if the timestamp is present, it is ignored.
The timestamp is required to prevent replay attacks, so in general, Oracle does not recommend setting this property to true except to address interoperability issues.
Controls whether OWSM requests a token lifetime when obtaining an issued token from a security token service (STS). When issued.token.caching is set to true, OWSM requests a token lifetime for returned tokens for the period specified by issued.token.lifetime. When it is set to false, OWSM does not request a token lifetime.
If the STS returns a token lifetime value different from the requested issued.token.lifetime value, OWSM uses the return value as the period for caching returned tokens. It the STS returns an empty token lifetime value, OWSM does not cache returned tokens despite issued.token.caching being set to true.
The time in milliseconds for OWSM to request as the token lifetime when obtaining an issued token from a security token service (STS). The domain default for this value is 28800000 milliseconds (eight hours). For information about how to change this default value, see "Configuring the Lifetime for the Issued Token Using Fusion Middleware Control".
The iteration count for key derivation.
The size of the key for key derivation.
Location of the client's keytab file.
The alias and password used for storing the decryption key password in the keystore.
If you set this value you then can override keystore.enc.csf.key, as described in "Overview of Policy Configuration Overrides".
If you do override this value, the key for the new value must be in the keystore. That is, overriding the value does not free you from the requirement of configuring the key in the keystores.
Keystore alias associated with the peer certificate. The security run time uses this alias to extract the peer certificate from the configured keystore and to encrypt messages to the peer. For information about overriding policies, see "Overview of Policy Configuration Overrides".
The alias and password used for storing the signature key password in the keystore. This property allows you to specify the signature key on a per-attachment level instead of at the domain level. This key is used when generating the enveloping signature, as specified using saml.envelope.signature.required flag.
Optional property. Action that will be used during attributes lookup. Value can be static or dynamic that uses ${} notation.
Optional property. Override this property to indicate whether the request is on behalf of an another entity. The default value for this flag is false.
When set to true and sts.auth.on.behalf.of.csf.key is configured, then it will be given preference and the identity established using that CSF key will be sent in the onBehalfOf token. If the sts.auth.on.behalf.of.username.only property is also set to true, the password portion of the identity in the CSF key will not be sent in the onBehalfOf token.
Otherwise, if the subject is already established, then the username from the subject will be sent as the onBehalfOf token.
If sts.auth.on.behalf.of.csf.key is not set and the subject does not exist, on.behalf.of is treated as a token exchange for the requestor and not for another entity. It is not included in an onBehalfOf element in the request.
Propagates the identity context from the Web service client to the Web service, and then makes it available ("publishes it") to other components for authentication and authorization purposes. For more information, see "Using SAML Policies to Propagate Identity Context".
HTTP Realm.
Note:
This property has no effect when defined as an unscoped override using the setWSMPolicySetOverride command. For more information, see "setWMSPolicySetOverride" in WLST Command Reference for Infrastructure Components.
Optional property that specifies the priority of the policy attachment. When specified for an attached policy, the effective set of policies algorithm allows the policy with the highest integer value priority to take precedence over a conflicting policy attachment, irrespective of its scope.
The value of reference.priority can be any number between(-231) and (231 - 1). The higher the number, the higher the priority assigned during effective policy calculation. Any policy that does not have a value or a non-numeric value is treated as having a value of 0. If the value is set to any of the words "yes", "true", or "on", the value is set to 1.
For more information, see "Specifying the Priority of a Policy Attachment".
Optional property that switches between different out-of-the-box mapping models. The default value is operation_as_action. Other allowed values are operation_as_resource_hierarchy and lookup_action_fixed_execute_action_as_operation.
Optional property. Resource name defined in OES. Value can be static or dynamic that uses ${} notation.
Optional property. Resource type defined in OES. Value can be static or dynamic that uses ${} notation.
Applies to Web service client only. If this is set, the body of protocol request messages such as createSequence() and terminateSequence() are encrypted. The default is that WS-RM protocol messages are not encrypted.
The response message body for protocol messages depends on the request message body: if the request message from the client is encrypted for protocol messages, the Web service sends the response encrypted, and vice versa.
SOAP role.
A non-null and non-empty salt for key derivation.
Name of the of the SAML token file.
Represents the relying party, as a comma-separated URI. This field accepts the following wildcards:
* in any location.
/* at the end of the URI.
.* at the end of the URI.
Flag that specifies whether the bearer token is signed using the domain signature key. You can override the domain signature key using the private signature key configured using keystore.sig.csf.key.
Set this flag false (in both client and service policy) to have the bearer token be unsigned.
SAML issuer URI. For more information, see "Adding an Additional SAML Assertion Issuer Name".
A comma-separated list of SAML token trusted issuers for an application that will override trusted issuers at domain level.
Secure Conversation token lifetime in milliseconds. The security context is shared by the client and Web service for the lifetime of a communication session. This is the time after which the SCT is expired.
Kerberos principal name that identifies the service.
Set subject.precedence to false to allow for the use of a client-specified username rather than the authenticated subject.
If subject.precedence is true, the user name to create the SAML assertion is obtained only from the Subject. Similarly, if subject.precedence is false, the user name to create the SAML assertion is obtained only from the csf-key username property.
Client's principal name as generated using the ktpass command and mapped to the username for which the kerberos token should be generated. It is of the format <username>@<REALM NAME>.
Location of the client's keytab file.
Optional property. Use to configure on behalf of entity. If present, it will be given preference over Subject (if it exists). For information about the on behalf of entity, see "on.behalf.of".
Optional property. Use to configure the on behalf of entity when sts.auth.on.behalf.of.csf.key is specified. For information about the on behalf of entity, see "on.behalf.of".
Principal name for the Web service that needs to be protected. It is of the format <host>/<machine name>@<REALM NAME>. For example, HTTP/mymachine@MYREALM.COM.
Use to configure username/password to authenticate to the STS.
If policy-reference-uri in the oracle/sts_trust_config_template client assertion template points to a username-based policy, then you configure the sts.auth.user.csf.key property to specify a username/password to authenticate to the STS.
Use to configure X509 certificate for authenticating to the STS.
If policy-reference-uri in the oracle/sts_trust_config_template client assertion template points to an x509-based policy, then you configure the sts.auth.x509.csf.key property to specify the X509 certificate for authenticating to the STS.
Use in Web Services Federation cases to specify the STSes in the trust chain from the RP-STS that web service trusts back to the IP-STS that the web client uses to authenticate.
Set the value of sts.in.order to a comma separated list of the STS URIs to be contacted, starting with the RP-STS and ending with the IP-STS.
For more information about using this property, see "Configuring Web Services Federation".
The alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.
Optional property. Set value to true to skip lookup phase. Does not apply to masking policy.
User attributes related to the principal of the SAML token.
Specify the attributes to be included as a comma-separated list. For example, attrib1,attrib2. The attribute names you specify must exactly match valid attributes in the configured identity store. The OWSM run time reads the values for these attributes from the configured identity store, and then includes the attributes and their values in the SAML assertion.
Requires that the Subject is available and subject.precedence is set to true.
A client policy reads the values of the attributes specified using user.attributes from the configured identity store. All valid attribute names and values are used to create the SAML attribute statement.
The user.attributes property is supported for a single identity store, and only the first identity store in the list is used. The user must, therefore, exist and be valid in the identity store used by the configured WebLogic Server Authentication provider. Authentication providers are described in "Configuring an Authentication Provider in WebLogic Server".
If the identity store you require is not the first identity store, you can specify that additional identity stores be searched. See "Including User Attributes in the Assertion" for more information.
User roles to be included.
When set to true, OWSM reads the roles of the user from the user repository (LDAP) and propagates them as SAML attributes.
Reserved for use with Oracle Cloud.