| Oracle® Fusion Middleware Security and Administrator's Guide for Web Services 11g Release 1 (11.1.1.6) Part Number B32511-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Security and Administrator's Guide for Web Services 11g Release 1 (11.1.1.6) Part Number B32511-07 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure policies in Web services and Web service clients to achieve Quality of Service (QoS) requirements.
The predefined policies are described in Appendix B, "Predefined Policies". This Appendix is the definitive source of information for the format of the policies. Some information from the Appendix is repeated here for your convenience.
This chapter includes the following sections:
Use the following series of questions to help you identify the security policies that best meet your requirements:
What are the basic requirements of your security policy? Decide if you need to only authenticate users, or if you only need message protection, or if you need both.
Do you require authentication only? If yes, then go to step 2.
Do you require authorization only? If yes, then see "Authorization Policies and Configuration Steps"
Do you require authentication and authorization? If yes, then go to step 3.
Do you only require message protection? If yes, then see "Message Protection-Only Policies and Configuration Steps".
Do you require both authentication and message protection? If yes, then go to step 4.
If you only require authentication, then there are two basic questions you need to consider:
Where will the token be inserted? Will the token to be inserted in the transport layer or in a SOAP header?
Do you need to use a particular type of token? The supported credentials for authentication-only policies are username/password, SAML, and Kerberos tokens.
If you require authentication and authorization, then you need to consider the following:
Review the considerations provided for authentication in step 2.
Review "Authorization Policies and Configuration Steps" for more information about authorization policies.
If you require both authentication and message protection, then you need to consider the following:
Will message protection be handled in the transport layer? If yes, then there are four sets of policies to choose from: Username over SSL, SAML over SSL (Sender-Vouches), SAML over SSL (Token Bearer), and HTTP token over SSL.
In one set of policies (wss_http_token_over_ssl_client_policy and wss_http_token_over_ssl_service_policy) authentication is also handled in the transport layer. For the other three polices, authentication takes place in the SOAP header.
If you are using the WS-Security V1.0 or V1.1 standard, then both authentication and message protection occur in the SOAP header. There are five pairs of policies supporting the following tokens: username/password, SAML, and X.509 certificates.
For more information, see "Message Protection and Authentication Policies and Configuration Steps".
Message protection involves encrypting the message for message confidentiality and signing the message for message integrity. Oracle Fusion Middleware predefined policies and any policy you create using one of the message-protection assertion templates provide the options for message confidentiality, message integrity, or both.
The following steps summarizes what you must do to configure the clients and services for message protection:
Attach the appropriate message protection policy to each of the clients and services.
If you want message integrity, then the message must be signed.
If you want message confidentiality, then the message must be encrypted.
Add the required public and private keys to the keystores of the clients and services. This step requires you to configure the keystore, as described in "Configuring Keystores for Message Protection".
Message protection encompasses two concepts, message confidentiality and message integrity.
Message confidentiality involves keeping the data secret, as well as the identities of the sending and receiving parties. Confidentiality is achieved by encrypting the content of messages and obfuscating the identities of the sending and receiving parties. The sender uses the recipient's public key to encrypt the message. Only the recipient's private key can successfully decrypt the message, ensuring that it cannot be read by third parties while in transit. The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
Message integrity is achieved by having an authority digitally sign the message. Digital signatures are used to authenticate the sender of the SOAP message and to ensure the integrity of the SOAP message (that is, to ensure that the SOAP message is not altered while in transit).
When a digital signature is applied to a SOAP message, a unique hash is produced from the message, and this hash is then encrypted with the sender's private key. When the message is received, the recipient decrypts the hash using the sender's public key.
Note:
Generally, the recipient does not need to have the sender's public key in its keystore to validate the certificate. It is sufficient to have the root certificate in the keystore to verify the certificate chain. However, if the sender's public key is not present in the message, as in the case of the Thumbprint and SerialIssuer mechanisms, the sender's public key must be in the recipient's keystore.This serves to authenticate the sender, because only the sender could have encrypted the hash with the private key. It also serves to ensure that the SOAP message has not been tampered with while in transit, because the recipient can compare the hash sent with the message with a hash produced on the recipient's end.
The message-protection assertion templates and predefined policies can be used to protect request and response messages by doing the following:
Signing messages
Encrypting messages
Signing and encrypting messages
Decrypting messages
Verifying signatures
Decrypting messages and verifying signatures
The Fusion Middleware Control user interface for the predefined message protection policies makes it easy to specify which message parts are signed, encrypted, or both. You can require that the entire body be signed, encrypted, or both, or identity specific header and body elements. The following is an example of partial encryption.
In this example, a part of the SOAP message is encrypted using Fusion Middleware Control:
Create a simple Web service that approves a credit card number (cardNr). A sample payload is shown in Example 11-1.
Example 11-1 Example of a Payload
<soapenv:Body wsu:Id="Body-2grW1pYwjwsoskbLuMJZzg22"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-ws
security-utility-1.0.xsd">
<aaav:validateTheCard xmlns:aaav="http://aaavalidatecred/">
<aaav:cardNr>string</aaav:cardNr>
<aaav:firstName>string</aaav:firstName>
<aaav:lastName>string</aaav:lastName>
<aaav:validUntilDate>string</aaav:validUntilDate>
</aaav:validateTheCard>
</soapenv:Body>
In Fusion Middleware Control, select a message protection policy and click Edit.
In the Settings tab, select the Request tab.
In the Message Encrypt Setting section, deselect Include Entire Body (Figure 11-1).
Expand Body Elements and click Add.
Enter the Namespace and the Element Name. In this example, only the card number is encrypted as follows:
Namespace = http://aaavalidatecred/
Element Name = //aaav:cardNr
For more information on other fields in the Edit Policy page, see Table C-92. Example 11-2 shows what the policy would look like.
Click Yes to add the Body Elements and Save to save the modified policy.
Figure 11-1 Example of Partial Encryption of Message Protection Policies
Packaging as attachments in SOAP messages has become common for any data that cannot be placed inside SOAP Envelope. The primary SOAP message can reference additional entities as attachments or attachments with MIME headers.
Each SwA attachment is a MIME part and contains the MIME header. Include SwA Attachment signs the attachment but not the MIME header corresponding to that. Include MIME Headers signs the corresponding MIME headers as well as the attachments.
The following policies offer message protection. The subsequent sections for each of these policies later in this chapter describe how each policy implements message protection.
oracle/wss10_message_protection_client_policy
oracle/wss10_message_protection_service_policy
oracle/wss10_username_id_propagation_with_msg_protection_client_policy
oracle/wss10_username_id_propagation_with_msg_protection_service_policy
oracle/wss10_username_token_with_message_protection_client_policy
oracle/wss10_username_token_with_message_protection_service_policy
oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy
oracle/wss10_username_token_with_message_protection_ski_basic256_service_policy
oracle/wss10_x509_token_with_message_protection_client_policy
oracle/wss10_x509_token_with_message_protection_service_policy
oracle/wss10_saml_token_with_message_protection_client_policy
oracle/wss10_saml_token_with_message_protection_service_policy
oracle/wss10_saml20_token_with_message_protection_client_policy
oracle/wss10_saml20_token_with_message_protection_service_policy
oracle/wss10_saml_hok_token_with_message_protection_client_policy
oracle/wss10_saml_hok_token_with_message_protection_service_policy
oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy
oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy
oracle/wss11_message_protection_client_policy
oracle/wss11_message_protection_service_policy
oracle/wss11_kerberos_token_with_message_protection_client_policy
oracle/wss11_kerberos_token_with_message_protection_service_policy
oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy
oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy
oracle/wss11_saml_token_with_message_protection_client_policy
oracle/wss11_saml_token_with_message_protection_service_policy
oracle/wss11_saml20_token_with_message_protection_client_policy
oracle/wss11_saml20_token_with_message_protection_service_policy
oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy
oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy
oracle/wss11_sts_issued_saml_with_message_protection_client_policy
oracle/wss11_username_token_with_message_protection_client_policy
oracle/wss11_username_token_with_message_protection_service_policy
oracle/wss11_x509_token_with_message_protection_client_policy
oracle/wss11_x509_token_with_message_protection_service_policy
Both the WS-Security 1.0 and WS-Security 1.1 standards are supported. Use the assertion template or predefined policy that supports the standard which both the Web service and client share in common. If you are starting anew, use the WS-Security 1.1 standard because it provides more options and requires less PKI deployment.
The assertion templates support partial signing and encryption as well as full signing and encryption of the message body. For those assertion templates or predefined policies that provide SOAP message protection, the default behavior is to protect the entire SOAP message body by signing and encrypting the entire SOAP body. You can configure the assertions and policies to protect selected elements, if you wish.
Table B-1 in Appendix B, "Predefined Policies" summarizes the security policies that enforce authentication only, and indicates whether the token is inserted at the transport layer or SOAP header.
This section lists the authentication-only predefined policies, indicates the type of Web service to which they apply, and provides a link to the configuration steps you must perform to use them.
The oracle/wss_http_token_client_policy policy includes credentials in the HTTP header for outbound client requests. It is the analogous client policy to the oracle/wss_http_token_service_policy service endpoint policy.
This policy contains the following assertion template: oracle/wss_http_token_client_template. See "oracle/wss_http_token_client_template" for more information about the assertion.
You can specify a value for csf-key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information on how to add the key to the credential store.
If you do not set the Require Mutual Authentication control, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
The client must pass the credentials in the HTTP header.
If you do not set the Require Mutual Authentication control, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
The wss_http_token_service_policy uses the credentials in the HTTP header to authenticate users.
This policy contains the following assertion template: oracle/wss_http_token_service_template. See "oracle/wss_http_token_service_template" for more information about the assertion.
The Web service must authenticate the supplied username and password credentials against the configured authentication source.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
For mutual SSL authentication, you must configure WebLogic Server. See "Configuring SSL on WebLogic Server (Two-Way)".
Note:
This policy is not secure; it transmits the password in clear text. You should use this policy 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 policy, oracle/wss_username_token_over_ssl_client_policy.This policy includes credentials in the WS-Security UsernameToken header for all outbound SOAP request messages. A plain text mechanism is supported, in addition to a password not being required. It is the analogous client policy to the oracle/wss_username_token_service_policy service endpoint policy.
This policy contains the following assertion template: oracle/wss_username_token_client_template. See "oracle/wss_username_token_client_template" for more information about the assertion.
You can specify a value for csf-key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information on how to add the key to the credential store.
If you specify a password type of None on the Settings page, you do not need to include a password in the key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
The client must include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.
Note:
This policy is not secure; it transmits the password in clear text. You should use this policy 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 policy, oracle/wss_username_token_over_ssl_service_policy.This policy uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users. The plain text mechanism is supported.
This policy contains the following assertion template: oracle/wss_username_token_service_template. See "oracle/wss_username_token_service_template" for more information about the assertion.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
Note:
This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.This policy includes SAML tokens in outbound SOAP request messages.
This policy contains the following assertion template: oracle/wss10_saml_token_client_template. See "oracle/wss10_saml_token_client_template" for more information about the assertion.
See "Configuring SAML".
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Include a WS-Security Header Element (<saml:Assertion>) that inserts a SAML token in the outbound SOAP message. The confirmation type is always sender-vouches.
Note:
This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.This policy authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss10_saml_token_service_template. See "oracle/wss10_saml_token_service_template" for more information about the assertion.
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the provider.
Note:
This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.This policy includes SAML tokens in outbound SOAP request messages.
This policy contains the following assertion template: oracle/wss10_saml20_token_client_template. See "oracle/wss10_saml20_token_client_template" for more information about the assertion.
See "Configuring SAML".
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Include a WS-Security Header Element (<saml:Assertion>) that inserts a SAML token in the outbound SOAP message. The confirmation type is always sender-vouches.
Note:
This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.This policy authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss10_saml20_token_service_template. See "oracle/wss10_saml20_token_service_template" for more information about the assertion.
Configure the saml2.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the provider.
This policy includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
Service principal names (SPN) are a key component in Kerberos authentication. SPNs are unique identifiers for services running on servers. Every service that uses Kerberos authentication needs to have an SPN set for it so that clients can identify the service on the network. If an SPN is not set for a service, clients have no way of locating that service and Kerberos authentication is not possible.
This policy contains the following assertion template: oracle/wss11_kerberos_token_client_template. See "oracle/wss11_kerberos_token_with_message_protection_client_template" for more information about the assertion.
The Web service client that is enforcing Kerberos client side policies needs to know the service principal name of the service it is trying to access. You can specify a value for service.principal.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The default value (place holder) is HOST/localhost@oracle.com.
You must set the service principal name. The service principal name specifies the name of the service principal for which the client requests a ticket from the KDC.
If the Kerberos authentication is successful, then send the obtained Kerberos ticket and authenticator to the Web service enclosed in a BinarySecurityToken element in the SOAP Security header.
This policy is enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
Service principal names (SPN) are a key component in Kerberos authentication. SPNs are unique identifiers for services running on servers. Every service that uses Kerberos authentication needs to have an SPN set for it so that clients can identify the service on the network. If an SPN is not set for a service, clients have no way of locating that service and Kerberos authentication is not possible.
This policy contains the following assertion template: oracle/wss11_kerberos_token_service_template. See "oracle/wss11_kerberos_token_with_message_protection_service_template" for more information about the assertion.
Configure the krb5.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
See "Protecting Messages" for a description of how the predefined policies implement message protection.
Table B-2 summarizes the policies that enforce only message protection, and indicates whether the policy is enforced at the transport layer or SOAP header.
Message protection-only policies do not authenticate or authorize the requester.
There may be either one or two Security policies attached to a policy subject. A Security policy can contain an assertion that belongs to the authentication or message protection (as in this case) subtype categories, or a single assertion that belongs to both subtype categories. You can then use an assertion that belongs to the authorization subtype to authorize the requester.
This policy provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_message_protection_client_template. See "oracle/wss10_message_protection_client_policy" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-3 WS-Security 1.0 Message Integrity of SOAP Message
<dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:SignedInfo>
<dsig:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<dsig:Reference URI="#Timestamp-...">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>...</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#Body-...">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>...</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#KeyInfo-...">
<dsig:Transforms>
<dsig:Transform
Algorithm="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform">
<TransformationParameters xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns="http://www.w3.org/2000/09/xmldsig#"/>
</TransformationParameters>
</dsig:Transform>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>...</dsig:DigestValue>
</dsig:Reference>
</dsig:SignedInfo>
<dsig:SignatureValue>....</dsig:SignatureValue>
<dsig:KeyInfo Id="KeyInfo-...">
<wsse:SecurityTokenReference xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier"
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">
...</wsse:KeyIdentifier>
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
</dsig:Signature>
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
Example 11-4 WS-Security 1.0 Message Confidentiality of SOAP Message
<env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Body-JA9fsCRnqbFJ0ocBAMKb7g22">
<xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="...">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/>
<xenc:CipherData>
<xenc:CipherValue>...</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</env:Body>
This policy enforces message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
The messages are protected using WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. This policy does not authenticate or authorize the requester.
This policy contains the following assertion template: oracle/wss10_message_protection_service_template. See "oracle/wss10_message_protection_service_template" for more information about the assertion.
See Table C-20. You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message integrity and confidentiality for outbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_message_protection_client_template. See "oracle/wss11_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.enc.csf.key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
This policy uses symmetric key technology, which is an encryption method that uses the same shared key to encrypt and decrypt data. The symmetric key is used to sign the message.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
Example 11-5 WS-Security 1.1 Message Confidentiality of SOAP Message
<xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="EK-...">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p">
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" />
</xenc:EncryptionMethod>
<dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1"
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">...</wsse:KeyIdentifier>
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>...</xenc:CipherValue>
</xenc:CipherData>
<xenc:ReferenceList>
<xenc:DataReference URI="#_..." />
</xenc:ReferenceList>
</xenc:EncryptedKey>
<env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Body-...">
<xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="...">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc" />
<dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Reference URI="#EK-..." ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" />
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>...</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</env:Body>
This policy enforces message integrity and confidentiality for inbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_message_protection_service_template. See "oracle/wss11_message_protection_service_template" for more information about the assertion.
See Table C-23. You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Table B-3 summarizes the policies that enforce both message protection and authentication, and indicates whether the policy is enforced at the transport layer or SOAP header. These polices are described in the sections that follow.
See "Protecting Messages" for a description of how the predefined policies implement message protection.
The following policies contain assertions as an OR group—meaning that either type of assertion can be enforced by a client:
oracle/wss11_saml_or_username_token_with_message_protection_service_policy
oracle/wss_saml_or_username_token_over_ssl_service_policy
oracle/wss_saml_or_username_token_service_policy
In addition, you can add an OR group to the policy of your choice, as described in "Adding an OR Group to a Policy".
The oracle/wss11_saml_or_username_token_with_message_protection_service_policy policy contains the following assertion templates:
oracle/wss11_saml_token_with_message_protection_service_template. For information about configuring the policy, see "oracle/wss11_saml_token_with_message_protection_service_policy".
oracle/wss11_username_token_with_message_protection_service_template. For information about configuring the policy, see "oracle/wss11_username_token_with_message_protection_service_policy".
oracle/wss_saml_token_bearer_over_ssl_service_template. For information about configuring the policy, see "oracle/wss_saml_token_bearer_over_ssl_service_policy".
oracle/wss_username_token_over_ssl_service_template. For information about configuring the policy, see "oracle/wss_username_token_over_ssl_service_policy".
oracle/wss_http_token_over_ssl_service_template. For information about configuring the policy, see "oracle/wss_http_token_over_ssl_service_policy".
The oracle/wss_saml_or_username_token_over_ssl_service_policy policy contains the following assertion templates:
oracle/wss_saml_token_over_ssl_service_template. For information about configuring the policy, see "oracle/wss_saml_token_over_ssl_service_policy".
oracle/wss_username_token_over_ssl_service_template. For information about configuring the policy, see "oracle/wss_username_token_over_ssl_service_policy".
The oracle/wss_saml_or_username_token_service_policy policy contains the following assertion templates:
oracle/wss_saml_token_service_template. For information about configuring the policy, see "oracle/wss10_saml_token_service_policy".
oracle/wss_username_token_service_template. For information about configuring the policy, see "oracle/wss_username_token_service_policy".
This policy includes credentials in the HTTP header for outbound client requests.
This policy also 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 endpoint.
Note:
Currently only HTTP basic authentication is supported.This policy contains the following assertion template: oracle/wss_http_token_over_ssl_client_template. See "oracle/wss_http_token_over_ssl_client_template" for more information about the assertion.
You can specify a value for csf-key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information on how to add the key to the credential store.
If you do not set the Require Mutual Authentication control, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
The client must pass the credentials in the HTTP header.
If you do not set the Require Mutual Authentication control, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy extracts the credentials in the HTTP header and authenticates users.
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 endpoint.
Note:
Currently only HTTP basic authentication is supported.This policy contains the following assertion template: oracle/wss_http_token_over_ssl_service_template. See "oracle/wss_http_token_over_ssl_service_template" for more information about the assertion.
Configure SSL, as described in "Configuring SSL on WebLogic Server (One-Way)", or as in "Configuring SSL on WebLogic Server (Two-Way)" if Allow Mutual Authentication is checked.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
This policy includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method Bearer is created automatically.
This policy contains the following assertion template: oracle/wss_saml_token_bearer_over_ssl_client_template. See "oracle/wss_saml_token_bearer_over_ssl_client_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss_saml_token_bearer_over_ssl_service_template. See "oracle/wss_saml_token_bearer_over_ssl_service_template" for more information about the assertion.
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
See "Configuring SAML".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
To configure SSL, see "Configuring SSL on WebLogic Server (One-Way)", or "Configuring SSL on WebLogic Server (Two-Way)" if Require Mutual Authentication is checked.
This policy includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method Bearer is created automatically.
This policy contains the following assertion template: oracle/wss_saml20_token_bearer_over_ssl_client_template. See "oracle/wss_saml20_token_bearer_over_ssl_client_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss_saml20_token_bearer_over_ssl_service_template. See "oracle/wss_saml20_token_bearer_over_ssl_service_template" for more information about the assertion.
Configure the saml2.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
See "Configuring SAML".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
To configure SSL, see "Configuring SSL on WebLogic Server (One-Way)", or "Configuring SSL on WebLogic Server (Two-Way)" if Require Mutual Authentication is checked.
This policy enables the authentication of credentials provided via a SAML token within WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss_saml_token_over_ssl_client_template. See "oracle/wss_saml_token_over_ssl_client_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss_saml_token_over_ssl_service_template. See "oracle/wss_saml_token_over_ssl_service_template" for more information about the assertion.
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
To configure SSL, see "Configuring SSL on WebLogic Server (One-Way)", or "Configuring SSL on WebLogic Server (Two-Way)" if Require Mutual Authentication is checked.
This policy enables the authentication of credentials provided via a SAML token within WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss_saml20_token_over_ssl_client_template. See "oracle/wss_saml20_token_over_ssl_client_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header.
This policy contains the following assertion template: oracle/wss_saml_token_over_ssl_service_template. See "oracle/wss_saml20_token_over_ssl_service_template" for more information about the assertion.
Configure the saml2.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
To configure SSL, see "Configuring SSL on WebLogic Server (One-Way)", or "Configuring SSL on WebLogic Server (Two-Way)" if Require Mutual Authentication is checked.
This policy includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages. The plain text mechanism is supported. The policy also uses SSL for achieving transport layer security.
This policy contains the following assertion template: oracle/wss_username_token_over_ssl_client_template. See "oracle/wss_username_token_over_ssl_client_template" for more information about the assertion.
If you do not set the Require Mutual Authentication control, one-way SSL is involved, as described in "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
You can specify a value for csf-key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information on how to add the key to the credential store.
If you specify a password type of None on the Settings page, you do not need to include a password in the key.
The client must include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
If you do not set the Require Mutual Authentication control, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users. The plain text mechanism is supported.
This policy contains the following assertion template: oracle/wss_username_token_over_ssl_service_template. See "oracle/wss_username_token_over_ssl_service_template" for more information about the assertion.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The username and password must exist and be valid.
To configure SSL, see "Configuring SSL on WebLogic Server (One-Way)", or "Configuring SSL on WebLogic Server (Two-Way)" if Require Mutual Authentication is checked.
This policy provides message-level protection and SAML holder of key based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml_hok_token_with_message_integrity_client_template. See "oracle/wss10_saml_hok_token_with_message_protection_service_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
Override the saml.assertion.filename property to point to the file that has the holder-of-key assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
Override the saml.assertion.filename property to point to the file that has the holder-of-key assertion. See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection and SAML holder of key based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml_hok_token_with_message_integrity_service_template. See "oracle/wss10_saml_hok_token_with_message_protection_service_template" for more information about the assertion.
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Note:
A CertificateExpiredException is returned if an expired certificate is present in the keystore, regardless of whether this certificate is being referenced. To resolve this exception, remove the expired certificate from the keystore.Store the trusted certificate of the SAML authority in the keystore.
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level integrity and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml_token_with_message_integrity_client_template. See "oracle/wss10_saml20_token_with_message_protection_client_template" for more information about the assertion.
See "Configuring SAML".
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
Include a WS-Security Header Element (<saml:Assertion>) that inserts a SAML token in the outbound SOAP message. The confirmation type is always sender-vouches.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml_token_with_message_protection_service_template. See "oracle/wss10_saml_token_with_message_protection_service_template" for more information about the assertion.
See Table C-51.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
This policy provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml_token_with_message_protection_client_template. See "oracle/wss10_saml_token_with_message_protection_client_template" for more information about the assertion.
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml_token_with_message_protection_service_template. See "oracle/wss10_saml_token_with_message_protection_service_template" for more information about the assertion.
See Table C-48.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_saml20_token_with_message_protection_client_template. See "oracle/wss10_saml20_token_with_message_protection_client_template" for more information about the assertion.
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_sam20l_token_with_message_protection_service_template. See "oracle/wss10_saml20_token_with_message_protection_service_template" for more information about the assertion.
See Table C-51.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the saml2.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.
This policy uses the Subject Key Identifier (ski) reference mechanism for the encryption key in the request, and for both the signature and encryption keys in the response.
This policy contains the following assertion template: oracle/wss10_saml_token_with_message_protection_client_template. See "oracle/wss10_saml_token_with_message_protection_client_template" for more information about the assertion.
Note:
Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 5.0 software have built-in restrictions on available cryptographic strength.By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0) file from http://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-142662.html.
To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:
US_export_policy.jar
local_policy.jar
You should back up your existing JAR files before replacing them.
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy uses the Subject Key Identifier (ski) reference mechanism for the encryption key in the request, and for both the signature and encryption keys in the response.
This policy contains the following assertion template: oracle/wss10_saml_token_with_message_protection_service_template. See "oracle/wss10_saml_token_with_message_protection_service_template" for more information about the assertion.
Note:
Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 5.0 software have built-in restrictions on available cryptographic strength.By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0) file from http://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-142662.html.
To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:
US_export_policy.jar
local_policy.jar
You should back up your existing JAR files before replacing them.
See Table C-48.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules" for more information.
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
How to Set Up Oracle Platform Security Services (OPSS)
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore. When using the ski reference mechanism, use OpenSSL or another such utility to create the certificate.
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level protection (that is, integrity and confidentiality) and identity propagation for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_username_id_propagation_with_msg_protection_client_template. See "oracle/wss10_username_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
The client must include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
Configure the policy assertion for message signing, message encryption, or both.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message level protection (that is, integrity and confidentiality) and identity propagation for inbound SOAP requests using mechanisms described in WS-Security 1.0.
This policy contains the following assertion template: oracle/wss10_username_id_propagation_with_msg_protection_service_template. See "oracle/wss10_username_token_with_message_protection_service_template" for more information about the assertion.
See Table C-55. You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
How to Set Up Oracle Platform Security Services (OPSS
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level protection (message integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_username_token_with_message_protection_client_template. See "oracle/wss10_username_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for csf-key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information on how to add the key to the credential store.
Configure the policy assertion for message signing, message encryption, or both.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection (message integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_username_token_with_message_protection_service_template. See "oracle/wss10_username_token_with_message_protection_service_template" for more information about the assertion.
See Table C-54. You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
How to Set Up Oracle Platform Security Services (OPSS)
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level protection (message integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy uses the Subject Key Identifier (ski) reference mechanism for the encryption key in the request, and for both the signature and encryption keys in the response.
This policy contains the following assertion template: oracle/wss10_username_token_with_message_protection_client_template. See "oracle/wss10_username_token_with_message_protection_client_template" for more information about the assertion.
Note:
Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 5.0 software have built-in restrictions on available cryptographic strength.By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0) file from http://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-142662.html.
To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:
US_export_policy.jar
local_policy.jar
You should back up your existing JAR files before replacing them.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for csf-key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information on how to add the key to the credential store.
Configure the policy assertion for message signing, message encryption, or both.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection (message integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy uses the Subject Key Identifier (ski) reference mechanism for the encryption key in the request, and for both the signature and encryption keys in the response.
This policy contains the following assertion template: oracle/wss10_username_token_with_message_protection_service_template. See "oracle/wss10_username_token_with_message_protection_service_template" for more information about the assertion.
Note:
Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 5.0 software have built-in restrictions on available cryptographic strength.By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0) file from http://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-142662.html.
To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:
US_export_policy.jar
local_policy.jar
You should back up your existing JAR files before replacing them.
See Table C-54. You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
How to Set Up Oracle Platform Security Services (OPSS)
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore. When using the ski reference mechanism, use OpenSSL or another such utility to create the certificate.
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
This policy provides message-level protection and certificate credential population for outbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_x509_token_with_message_protection_client_template. See "oracle/wss10_x509_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
The Web service client needs to provide valid X.509 authentication credentials in the SOAP message through the WS-Security binary security token.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-3 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.
Example 11-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.
This policy enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.
This policy contains the following assertion template: oracle/wss10_x509_token_with_message_protection_service_template. See "oracle/wss10_x509_token_with_message_protection_service_template" for more information about the assertion.
See Table C-57. You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Attaching Web Service Policies Permitting Overrides".
How to Set Up WebLogic Server
You need to configure an Authentication provider, as described in "Configuring an Authentication Provider in WebLogic Server".
This policy includes a Kerberos token in the WS-Security header, and uses Kerberos keys to guarantee message integrity and confidentiality, in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
This policy contains the following assertion template: oracle/wss11_kerberos_token_with_message_protection_client_template. See "oracle/wss11_kerberos_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
Also see "Using Kerberos Tokens".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore".
Also see "Using Kerberos Tokens".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy is enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
This policy contains the following assertion template: oracle/wss11_kerberos_token_with_message_protection_service_template. See "oracle/wss11_kerberos_token_with_message_protection_service_template" for more information about the assertion.
You have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the krb5.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure Kerberos, as described in "Using Kerberos Tokens".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
This policy includes a Kerberos token in the WS-Security header, and uses Kerberos keys to guarantee message integrity and confidentiality, in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
The policy uses Basic128 as the algorithm suite.
This policy contains the following assertion template: oracle/wss11_kerberos_token_with_message_protection_client_template. See "oracle/wss11_kerberos_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
Also see "Using Kerberos Tokens".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore".
Also see "Using Kerberos Tokens".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy is enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard.
The policy uses Basic128 as the algorithm suite.
This policy contains the following assertion template: oracle/wss11_kerberos_token_with_message_protection_service_template. See "oracle/wss11_kerberos_token_with_message_protection_service_template" for more information about the assertion.
You have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the krb5.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure Kerberos, as described in "Using Kerberos Tokens".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
This policy enables identity switching. Identity switching means that the policy propagates a different identity than the one based on the authenticated Subject. Instead of using the username from the Subject, this policy allows you to set a new user name when sending the SAML Web service request.
This policy enables message level protection and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.
This policy contains the following assertion template: oracle/wss11_saml_token_with_message_protection_client_template. See "oracle/wss11_saml_token_with_message_protection_client_template" for more information about the assertion.
You attach the wss11_saml_token_identity_switch_with_message_protection_client_policy to a Web service client of any type.
subject.precedence is set to false to allow for the use of a client-specified username rather than the authenticated subject. (If subject.precedence is false, the user name to create the SAML assertion is obtained only from the csf-key username property.) The wss11_saml_token_identity_switch_with_message_protection_client_policy policy requires that an application to which the policy is attached must have the WSIdentityPermission permission. That is, applications from which Oracle WSM accepts the externally-supplied identity must have the WSIdentityPermission permission. This is to avoid potentially rogue applications from providing an identity to Oracle WSM.
See "Configuring SAML Web Service Clients for Identity Switching" for information about how to use this policy. In particular, you need to "Set the javax.xml.ws.security.auth.username Property", and "Set the WSIdentityPermission Permission".
See "How to Configure SAML Web Service Client at Design Time" for additional SAML considerations.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for saml.audience.uri on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy enables message level protection and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.
This policy contains the following assertion template: oracle/wss11_saml_token_with_message_protection_client_template. See "oracle/wss11_saml_token_with_message_protection_client_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_saml_token_with_message_protection_service_template. See "oracle/wss11_saml_token_with_message_protection_service_template" for more information about the assertion.
See Table C-62.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the saml.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules".
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
This policy enables message level protection and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.
This policy contains the following assertion template: oracle/wss11_saml20_token_with_message_protection_client_template. See "oracle/wss11_saml20_token_with_message_protection_client_template" for more information about the assertion.
See "How to Configure SAML Web Service Client at Design Time".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
You can specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.
You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
See "How to Configure SAML Web Service Client at Design Time".
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_saml20_token_with_message_protection_service_template. See "oracle/wss11_saml20_token_with_message_protection_service_template" for more information about the assertion.
See Table C-65.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the saml2.loginmodule login module. See "Configuring the SAML and Kerberos Login Modules".
See "Configuring SAML".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
The SAML login module extracts the username from the verified token and passes it to the Authentication provider.
This policy provides message-level protection and authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_username_token_with_message_protection_client_template. See "oracle/wss11_username_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.enc.csf.key on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.
This policy uses symmetric key technology, which is an encryption method that uses the same shared key to encrypt and decrypt data. The symmetric key is used to sign the message.
Configure the policy assertion for message signing, message encryption, or both.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy enforces message-level protection (that is, message integrity and message confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_username_token_with_message_protection_service_template. See "oracle/wss11_username_token_with_message_protection_service_template" for more information about the assertion.
See Table C-68. You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
How to Set Up WebLogic Server
Use the WebLogic Server Administration Console to add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".
This policy provides message-level protection and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_x509_token_with_message_protection_client_template. See "oracle/wss11_x509_token_with_message_protection_client_template" for more information about the assertion.
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the Oracle WSM keystore, as described in "Configuring Keystores for Message Protection".
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.sig.csf.key and keystore.enc.csf.key on the Configurations page, or override them on a per-client basis using the Security Configuration Details control when you attach the policy.
This policy requires you to set up the Web service client keystore, as described in "Setting Up the Web Service Client Keystore". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.
The Web service client needs to provide valid X.509 authentication credentials in the SOAP message through the WS-Security binary security token.
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
Example 11-5 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.
This policy enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.
This policy contains the following assertion template: oracle/wss11_x509_token_with_message_protection_service_template. See "oracle/wss11_x509_token_with_message_protection_service_template" for more information about the assertion.
See Table C-71. You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
Configure the policy assertion for message signing, message encryption, or both.
This policy requires you to set up the keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.
You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.
You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
How to Set Up WebLogic Server
You need to configure the Authentication provider, as described in "Configuring an Authentication Provider in WebLogic Server".
Frequently, authentication is the first step of determining whether a user should be given access to a Web service. After the user is authenticated, the second step is to verify that the user is authorized to access the Web service. This is accomplished using an authorization policy. You can create an authorization policy using the binding_authorization_template or the component_authorization_template assertion templates.
Policies created with these templates perform role- or permission-based access control (RBAC) and check that the authenticated user has been granted one of the roles or permissions allowed access to the Web service.
Appendix B, "Predefined Policies" summarizes the security policies that enforce authorization, and indicates whether the policy is enforced at the transport layer or SOAP header.
Note:
The authorization polices can follow any authentication policy where the subject is established.You cannot attach both a permitall and denyall policy to the same Web service.
The authorization policies provide the following properties that you can use to specify which resources you want the policy to protect. Not all of the predefined policies feature all of the properties.
Constraint Pattern -- 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. The only 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. For details about adding this header to a request, see "Configuring Oracle HTTP Server to Specify Request Origin".
Note the following:
The Constraint Pattern properties and their values are case sensitive.
The constraint expression uses the following standard supported operators: ==, !=, &&, || and !.
In the following example, the role-based authorization assertion will be executed only if the current message does not contain a SAML_SV token OR the request origin is not internal.
${!(messageContext.authenticationMethod =='SAML_SV'|| messageContext.requestOrigin == 'internal')}
Note:
This property is valid for authorization policies based on the binding_authorization_template only. For policies based on other authorization assertion templates, this property is reserved for future use.Action Pattern -- The Web service operation for which permission-based checks are performed. This value can be a comma-separated list of values. This field accepts wildcards. * means all Web service operations.
The valid values for Action Pattern are determined by the Web service methods. For example, if the Web service method is validate(amountAvailable), enter the Action Pattern as validate.
Resource Pattern -- The name of the resource for which permission-based checks are performed. This field accepts wildcards, and the default is * for all resources in the Web services protected by the policy.
By convention you enter the Resource Pattern as (namespace of Web service + Web service name).
For example, if the namespace of the Web service is http://project11 and the Web service name is CreditValidation, you would enter the Resource Name as http://project11/CreditValidation.
If you specify a specific Resource Pattern, the policy is enforced only for those Web services that match the criteria. That is, entering a specific Resource Pattern limits the scope of the authorization policy. This condition also applies if you have bulk-attached this authorization policy to multiple subjects. The default of * protects all resources (namespace of Web service + Web service name) of the bulk-attached Web services.
Permission Check Class -- By default, it is oracle.wsm.security.WSFunctionPermission. The class must be in the classpath.
Authorization Setting -- Possible values are Permit All, Deny All, and Selected Roles. If you choose Selected Roles, you must then select from the enterprise (Global) roles defined in WebLogic Server, which may include the following:
AdminChannelUser
Anonymous
AppTester
CrossDomainConnector
Deployer
Monitor
Operator
OracleSystemRole
Conceptually, determining whether an authenticated subject is authorized to access a particular resource protected by a Web service policy has two parts that work in tandem.
The Resource Pattern, and Action Pattern parameters on the Policy Settings page for the policy determine what resources are being protected by the policy, as shown in Figure 11-2. (You can also override the Resource Pattern and Action Pattern properties, as described in "Configuring Server-Side Override Properties for Authorization Policies".)
You have the option to change the Permission Check 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://java.sun.com/j2se/1.5.0/docs/api/java/security/Permission.html. The default is oracle.wsm.security.WSFunctionPermission.
Figure 11-2 The Permission Settings for a Policy
The OPSS Application Policies page specifies whether the authenticated subject has invoke access to the Resource Name listed there, as shown in Figure 11-3.
Figure 11-3 Adding a Permission on the OPSS Create Application Grant Page
OPSS uses the Policy Settings page for the Web service to determine which resources require an authorization check. Then, access to the resource is allowed if the authenticated subject has been granted WSFunctionPermission (or other permission) for that resource via OPSS.
Note:
If you changed the Permission Check Class configuration property for the policy to a custom class, use the custom class here as well.Consider further the example shown in Figure 11-2 and Figure 11-3.
On the Policy Settings page, assume that you specify the following to protect the validate method of the http://project11/CreditValidation Web service:
Action pattern: validate Resource pattern: http://project11/CreditValidation Permission Check Class oracle.wsm.security.WSFunctionPermission
Then, on the OPSS Application Policies page, you would use http://project11/CreditValidation#validate for the Resource Name to specify that the authenticated subject has permission to invoke this resource:
Permission Class: oracle.wsm.security.WSFunctionPermission Resource Name: http://project11/CreditValidation#validate Permissions Action: invoke
You can grant the WSFunctionPermission permission to a user, a group, or an application role. If you grant WSFunctionPermission to a user or group it will apply to all applications that are deployed in the domain.
In previous releases of Fusion Middleware Control, the Resource Name on the OPSS Application Policies page was determined by name-space-of-webservice/ServiceName. For example, if the name space of a Web service was http://project1/ and the service name was CreditValidation, the Resource Name would have been http://project1/CreditValidation. You could also use an asterisk (*) wildcard for providing permission to all the actions or all resources.
In this release, the resource target of the WSFunctionPermission is enhanced to include the actual Web service operation name. The syntax for the Resource Name is now name-space-of-webservice/servicename#[operation name]. (For a component it is compositename/componentname#[operation name].)]
You must now include at least the name-space-of-webservice/service name. That is, you can no longer use an asterisk (*) wildcard for providing permission to all the actions or all resources.
Instead, to specify all operations for a Web service, simply leave the operation name blank. For example, name-space-of-webservice/servicename#
Permission Action is always invoke.
This policy provides a simple role-based authorization policy based on the authenticated subject.
This policy denies all users with any role.
This policy should follow an authentication policy where the subject is established and can be attached to any SOAP-based endpoint.
You must have already configured a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy contains the following assertion template: oracle/binding_authorization_template
See "oracle/binding_authorization_template" for more information about the assertion.
See Table C-86.
To add roles:
Click Selected Roles.
Click Add.
To add roles, click the check box 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 check box 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.
If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. You use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Help.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy provides a simple role-based authorization policy based on the authenticated subject.
This policy permits all users with any roles.
This policy should follow an authentication policy where the subject is established and can be attached to any SOAP-based endpoint.
You must have already configured a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy contains the following assertion template: oracle/binding_authorization_template. See "oracle/binding_authorization_template" for more information about the assertion.
See Table C-86.
To add roles:
Click Selected Roles.
Click Add.
To add roles, click the check box 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 check box 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.
If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. You use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Help.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy provides a permission-based authorization policy based on the authenticated subject.
This policy ensures that the subject has permission to perform the operation. To do this, the Authorization Policy executor leverages OPSS to check if the authenticated subject has been granted oracle.wsm.security.WSFunctionPermission (or whatever permission class is specified in Permission Check Class) using the Resource Pattern and Action Pattern as parameters.
This policy should follow an authentication policy where the subject is established and can be attached to any SOAP-based endpoint.
This policy contains the following assertion template: oracle/binding_permission_authorization_template. See "oracle/binding_permission_authorization_template" for more information about the assertion.
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://java.sun.com/j2se/1.5.0/docs/api/java/security/Permission.html.
The default is oracle.wsm.security.WSFunctionPermission.
Use Fusion Middleware Control to grant the WSFunctionPermission (or other) permission to the user, group, or application that will attempt to authenticate to the Web service.
You have the option to change the permission_class configuration property for the policy, which identifies the permission class as per JAAS standards. The class must be available in the server classpath. The default is oracle.wsm.security.WSFunctionPermission.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy provides a simple role-based authorization policy based on the authenticated subject.
This policy denies all users with any roles.
You must have already configured a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy should follow an authentication policy where the subject is established and can be attached to any SCA-based endpoint.
This policy contains the following assertion template: oracle/component_authorization_template. See "oracle/component_authorization_template" for more information about the assertion.
See Table C-89.
To add roles:
Click Add.
To add roles, click the check box 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 check box 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.
If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. You use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Help.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy provides a simple role-based authorization policy based on the authenticated subject.
This policy permits all users with any roles.
You must have already configured a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
It should follow an authentication policy where the subject is established and can be attached to any SCA-based endpoint.
This policy contains the following assertion template: oracle/component_authorization_template. See "oracle/component_authorization_template" for more information about the assertion.
See Table C-89.
To add roles:
Click Add.
To add roles, click the check box 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 check box 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.
If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. You use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Help.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy provides a permission-based authorization policy based on the authenticated subject.
This policy ensures that the subject has permission to perform the operation. To do this, the Authorization Policy executor leverages OPSS to check if the authenticated subject has been granted oracle.wsm.security.WSFunctionPermission (or whatever permission class is specified in Permission Check Class) using the Resource Pattern and Action Pattern as parameters. Resource Pattern and Action Pattern are used to identify if the authorization assertion is to be enforced for this particular request. Access is allowed if the authenticated subject has been granted WSFunctionPermission.
You can grant the WSFunctionPermission permission to a user, a group, or an application role. If you grant WSFunctionPermission to a user or group it will apply to all applications that are deployed in the domain.
This policy should follow an authentication policy where the subject is established and can be attached to any SCA-based endpoint.
This policy contains the following assertion template: oracle/component_permission_authorization_template. See "oracle/component_permission_authorization_template" for more information about the assertion.
Use Fusion Middleware Control to grant the WSFunctionPermission permission to the user, group, or application that will attempt to authenticate to the Web service.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
This policy is a special case of role-based authorization policy based on the authenticated subject.
This policy will let requests in only if one of the following conditions is true:
The authenticated token is SAML Sender Vouches.
The user is in a particular role (the default is trustedEnterpriseRole, that establishes the user as a trusted entity
The request is coming from within a private network.
This policy can be attached to any SOAP-based endpoint.
This policy contains the following assertion template: oracle/binding_authorization_template.
See "oracle/binding_authorization_template" for more information about the assertion.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
See Table C-86.
To add roles:
Click Add.
To add roles, click the check box 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 check box 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.
If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. You use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Help.
You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Help.
To successfully invoke a service that has the whitelist_authorization_policy attached, you must do one of the following:
If the service accepts SAML sender vouches for authentication (for example, a SAML token service policy is attached to the service), you must attach the corresponding SAML token client policy to the client.
If the service accepts username/password for authentication (for example, a username token service policy is attached to the service), you must attach the corresponding username token client policy to the client and make sure that the client is in a trusted role as defined in the policy. (By default, the role defined in the predefined policy is trustedEnterpriseRole. You need to modify this role in the predefined policy.)
If the service is invoked using Oracle HTTP Server, and it is configured to indicate that the request came from a private internal network (see "Configuring Oracle HTTP Server to Specify Request Origin"), then a client on the internal network only has to attach the corresponding username token client policy at the client side.
The Constraint Pattern property setting contains a requestOrigin field that specifies 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.
To do so, the administrator must modify the httpd.conf file as follows:
Verify that the module mod_headers is loaded.
Set the VIRTUAL_HOST_TYPE header name in the RequestHeader. Valid values are internal and external. Use the following command syntax:
RequestHeader set|append|add|unset header [value [env=[!]variable]]
For example, to configure the virtual host for internal requests:
<VirtualHost *:7777> RequestHeader set VIRTUAL_HOST_TYPE "internal" </VirtualHost>
To configure the virtual host for external requests:
<VirtualHost *:8888> RequestHeader set VIRTUAL_HOST_TYPE "external" </VirtualHost>
In these examples, all the requests coming from outside of the private network are routed through virtual host:8888 and all the requests coming from the internal private network are routed through virtual host:7777.
Note that you must also add these ports in the httpd.conf file as listen ports so that the applications are available on the ports externally.
Restart the Oracle HTTP Server.
The Web Services Addressing (WS-Addressing) specification (http://www.w3.org/TR/ws-addr-core/) provides transport-neutral mechanisms to address Web services and messages. In particular, the specification defines a number of XML elements used to identify Web service endpoints and to secure end-to-end endpoint identification in messages.
This section describes the predefined WS-Addressing policies.
This policy causes the platform to check inbound messages for the presence of WS-Addressing headers conforming to the W3C 2005 Final WS-Addressing Policy standard. In addition, it causes the platform to include a WS-Addressing header in outbound SOAP messages.
Configure WS-Addressing for the Web service client as described in the Web Services Addressing 1.0 - SOAP Binding specification (http://www.w3.org/TR/ws-addr-soap/).
This section describes the predefined WS-Trust policies. The predefined policies conform to the WS-Trust 1.3 specification.
Use this policy to specify the STS configuration information that is used to invoke the STS for token exchange.
This policy contains the following assertion template: oracle/sts_trust_config_service_template. See "oracle/sts_trust_config_service_template" for more information about the assertion.
The oracle/sts_trust_config_service_policy policy assertion is as follows:
<?xml version = '1.0' encoding = 'UTF-8'?>
<wsp:Policy
xmlns:oralgp = "http://schemas.oracle.com/ws/2006/01/loggingpolicy"
xmlns:orasp = "http://schemas.oracle.com/ws/2006/01/securitypolicy"
orawsp:description = "i18n:oracle.wsm.resources.policydescription.PolicyDescriptionBundle_oracle/sts_
trust_config_service_policy_PolyDescKey"
orawsp:displayName = "i18n:oracle.wsm.resources.policydescription.PolicyDescriptionBundle_oracle/sts_
trust_config_service_policy_PolyDispNameKey"
wsu:Id = "sts_trust_config_service_policy"
orawsp:attachTo = "binding.server"
orawsp:status = "enabled"
xmlns:orawsp = "http://schemas.oracle.com/ws/2006/01/policy"
Name = "oracle/sts_trust_config_service_policy"
xmlns:wsp = "http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsu = "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
orawsp:category = "security"
orawsp:local-optimization = "off">
<orasp:sts-trust-config
orawsp:Silent = "true"
orawsp:Enforced = "true"
orawsp:name = "STS Trust Configuration"
orawsp:category = "security/sts-config"
orasp:wsdl-uri = "http://host:port/sts?wsdl"
orasp:port-uri = "http://host:port/sts-service"
orasp:soap-version="12">
<orawsp:bindings>
<orawsp:Config orawsp:name = "StsTrustConfig" orawsp:configType = "declarative">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:name="role" orawsp:type="string" orawsp:contentType="constant">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:sts-trust-config>
</wsp:Policy>
See "Setting Up Automatic Policy Configuration for STS" for the steps to follow.
Use this policy to specify the STS client configuration information that is used to invoke the STS for token exchange.
Use this policy only if you are not using Automatic (Client STS) Policy Configuration, as described in "Setting Up Automatic Policy Configuration for STS"
If you attach multiple instances of oracle/sts_trust_config_client_policy, no error is generated. However, only one instance is enforced, and you cannot control which instance that is.
This policy contains the following assertion template: oracle/sts_trust_config_template. See "oracle/sts_trust_config_client_template" for more information about the assertion.
The oracle/sts_trust_config_client_policy policy assertion is as follows:
<?xml version = '1.0' encoding = 'UTF-8'?>
<wsp:Policy
xmlns:oralgp = "http://schemas.oracle.com/ws/2006/01/loggingpolicy"
xmlns:orasp = "http://schemas.oracle.com/ws/2006/01/securitypolicy"
orawsp:description =
"i18n:oracle.wsm.resources.policydescription.PolicyDescriptionBundle_oracle/sts_trust_config_client_policy_PolyDescKey"
orawsp:displayName =
"i18n:oracle.wsm.resources.policydescription.PolicyDescriptionBundle_oracle/sts_trust_config_client_policy_PolyDispNameKey"
wsu:Id = "sts_trust_config_client_policy"
orawsp:attachTo = "binding.client"
orawsp:status = "enabled"
xmlns:orawsp = "http://schemas.oracle.com/ws/2006/01/policy"
Name = "oracle/sts_trust_config_client_policy"
xmlns:wsp = "http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsu = "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
orawsp:category = "security"
orawsp:local-optimization = "off">
<orasp:sts-trust-config
orawsp:Silent = "true"
orawsp:Enforced = "true"
orawsp:name = "STS Trust Configuration"
orawsp:category = "security/sts-config"
orasp:wsdl-uri = "http://host:port/sts?wsdl"
orasp:port-uri = "http://host:port/sts-service"
orasp:port-endpoint="target-namespace#wsdl.endpoint(service-name/port-name)"
orasp:policy-reference-uri="oracle/policy-name"
orasp:soap-version="12"
orasp:sts-keystore-recipient-alias="sts-csf-key">
<orawsp:bindings>
<orawsp:Config orawsp:name = "StsTrustConfig" orawsp:configType = "declarative">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:name="role" orawsp:type="string" orawsp:contentType="constant">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:sts-trust-config>
</wsp:Policy>
You are encouraged to configure the STS config policy from the Web service, as described in "Setting Up Automatic Policy Configuration for STS".
However, if you did not configure the STS config policy from the Web service, or if you are using the SAML sender vouches confirmation method, you must then configure it from the Web service client. See "Manually Configuring the STS Config Policy From the Web Service Client: Main Steps" for information on how to set up the Web service client.
You are encouraged to configure the STS config policy from the Web service, as described in "Setting Up Automatic Policy Configuration for STS".
However, if you did not configure the STS config policy from the Web service, or if you are using the SAML sender vouches confirmation method, you must then configure it from the Web service client as described in this section.
See "Manually Configuring the STS Config Policy From the Web Service Client: Main Steps" for additional information on how to set up the Web service client.
You can set up and attach the oracle/sts_trust_config_client_policy policy programmatically, as shown in Example 11-6 and Example 11-7.
Example 11-6 Sample JSE Proxy Client
URL endpointUrl = new URL(getWebConnectionString() + "/jaxws-test-service/jaxws-test-port");
ServiceDelegateImpl client = new ServiceDelegateImpl(
new URL(endpointUrl.toString() + "?WSDL"),
new QName("http://jaxws.oracle.com/targetNamespace/JaxwsService", "JaxwsService"),
OracleService.class);
JaxwsService port = client.getPort(
new QName("http://jaxws.oracle.com/targetNamespace/JaxwsService", "JaxwsServicePort"),
test.jaxws.client.JaxwsService.class);
((BindingProvider)port).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,endpointUrl.toExternalForm());
((BindingProvider)port).getRequestContext().put(ClientConstants.CLIENT_CONFIG,
fileToElement(new File("./jaxws/client/dat/oracle-webservice-client.xml")));
The related oracle-webservice-client.xml file with the STS config policy and STS issue policy is shown in Example 11-7.
Example 11-7 Sample oracle-webservice-client.xml
<?xml version="1.0" encoding="UTF-8"?>
<oracle-webservice-clients>
<webservice-client>
<port-info>
<policy-references>
<policy-reference uri="oracle/sts_trust_config_client_policy" category="security"/>
<policy-reference uri="oracle/wss11_sts_issue_saml_hok_with_message_protection_client_policy " category="security"/>
</policy-references>
</port-info>
</webservice-client>
</oracle-webservice-clients>
See "Setting Up Automatic Policy Configuration for STS" for the steps to follow.
This policy inserts a SAML bearer assertion issued by a trusted STS. Messages are protected using SSL.
This policy contains the following assertion template: oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy_template. See "WS-Trust Assertion Templates" for more information about the assertion.
The oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy assertion is as follows:
<orasp:wss-sts-issued-token-over-ssl xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy" xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" orasp:require-applies-to="true" orasp:require-client-entropy="true" orasp:require-server-entropy="true" orasp:trust-version="13" orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="security/authentication, security/msg-protection" orawsp:name="WS-Security 1.1, issued token over ssl"> <orasp:issued-token orasp:require-external-reference="true" orasp:require-internal-reference="true" orasp:use-derived-keys="false"> <orasp:request-security-token-template orasp:key-type="Bearer" orasp:token-type="SAML11"/> </orasp:issued-token> <orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/> <orawsp:bindings> <orawsp:Config orawsp:configType="declarative" orawsp:name="WssStsIssuedTokenOverSSLConfig"> <orawsp:PropertySet orawsp:name="standard-security-properties"> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.user.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.x509.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:name="on.behalf.of" orawsp:type="boolean"> <orawsp:Value>false</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.on.behalf.of.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.service.principal.name" orawsp:type="string"> <orawsp:Value>HOST/localhost@EXAMPLE.COM</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.keytab.location" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.caller.principal.name" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> </orawsp:PropertySet> </orawsp:Config> </orawsp:bindings> </orasp:wss-sts-issued-token-over-ssl>
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service client.
This policy requires you to set up the Oracle WSM keystore to specify a key (username/password or X.509) to authenticate to the STS. See "Configuring Keystores for Message Protection".
See "Programmatic Configuration Overrides for WS-Trust Client Policies" for a description of the configuration settings you can override.
If you do not set Require Mutual Authentication, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set Require Mutual Authentication, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service client.
This policy requires you to set up the Oracle WSM keystore to specify a key (username/password or X.509) to authenticate to the STS. See "Configuring Keystores for Message Protection".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override. See "Programmatic Configuration Overrides for WS-Trust Client Policies" for examples of overriding STS configuration settings.
If you do not set Require Mutual Authentication, one-way SSL is involved. See "Configuring SSL for a Web Service Client".
If you do set the Require Mutual Authentication control, the client must supply credentials, and expect credentials back from the Web service. See "Configuring Two-Way SSL for a Web Service Client".
This policy authenticates a SAML bearer assertion issued by a trusted STS. Messages are protected using SSL.
This policy contains the following assertion template: oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy_template. See "WS-Trust Assertion Templates" for more information about the assertion.
The oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy assertion is as follows:
<orasp:wss-sts-issued-token-over-ssl xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy" xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" orasp:require-applies-to="true" orasp:require-client-entropy="true" orasp:require-server-entropy="true" orasp:trust-version="13" orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="security/authentication, security/msg-protection" orawsp:name="WS-Security 1.1, issued token over ssl"> <orasp:issued-token orasp:require-external-reference="true" orasp:require-internal-reference="true" orasp:use-derived-keys="false"> <orasp:request-security-token-template orasp:key-type="Bearer" orasp:token-type="SAML11"/> </orasp:issued-token> <orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/> <orawsp:bindings> <orawsp:Config orawsp:configType="declarative" orawsp:name="WssStsIssuedTokenOverSSLConfig"> <orawsp:PropertySet orawsp:name="standard-security-properties"> <orawsp:Property orawsp:contentType="constant" orawsp:name="role" orawsp:type="string"> <orawsp:Value>ultimateReceiver</orawsp:Value> </orawsp:Property> </orawsp:PropertySet> </orawsp:Config> </orawsp:bindings> </orasp:wss-sts-issued-token-over-ssl>
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service.
To configure SSL, see "Configuring SSL on WebLogic Server (One-Way)", or "Configuring SSL on WebLogic Server (Two-Way)" if Require Mutual Authentication is checked.
This policy inserts a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using proof key material provided by the STS.
This policy contains the following assertion template: oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template. See "WS-Trust Assertion Templates" for more information about the assertion.
The oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy assertion is as follows:
<orasp:wss11-sts-issued-token-with-certificates xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy" xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" orasp:require-applies-to="true" orasp:require-client-entropy="true" orasp:require-server-entropy="true" orasp:trust-version="13" orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="security/authentication, security/msg-protection" orawsp:name="WS-Security 1.1, issued tokee"> <orasp:issued-token orasp:require-external-reference="true" orasp:require-internal-reference="true" orasp:use-derived-keys="false"> <orasp:request-security-token-template orasp:algorithm-suite="Basic128" orasp:key-type="Symmetric" orasp:token-type="SAML11"/> </orasp:issued-token> <orasp:x509-token orasp:enc-key-ref-mech="thumbprint" orasp:is-encrypted="false" orasp:is-signed="true" orasp:sign-key-ref-mech="thumbprint"/> <orasp:msg-security orasp:algorithm-suite="Basic128" orasp:confirm-signature="true" orasp:encrypt-signature="false" orasp:include-timestamp="true" orasp:sign-then-encrypt="true" orasp:use-derived-keys="false"> <orasp:request> <orasp:signed-parts> <orasp:body/> <orasp:header orasp:namespace="http://www.w3.org/2005/08/addressing"/> <orasp:header orasp:namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/> <orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/> </orasp:signed-parts> <orasp:encrypted-parts> <orasp:body/> <orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/> </orasp:encrypted-parts> </orasp:request> <orasp:response> <orasp:signed-parts> <orasp:body/> </orasp:signed-parts> <orasp:encrypted-parts> <orasp:body/> </orasp:encrypted-parts> </orasp:response> <orasp:fault/> </orasp:msg-security> <orawsp:bindings> <orawsp:Config orawsp:configType="declarative" orawsp:name="Wss11StsIssuedTokenWithCertsConfig"> <orawsp:PropertySet orawsp:name="standard-security-properties"> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.user.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.x509.csf.key" orawsp:type="string"> <orawsp:Value>enc-csf-key</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:name="on.behalf.of" orawsp:type="boolean"> <orawsp:Value>false</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.on.behalf.of.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:name="keystore.recipient.alias" orawsp:type="string"> <orawsp:Value>orakey</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="keystore.enc.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.service.principal.name" orawsp:type="string"> <orawsp:Value>HOST/localhost@EXAMPLE.COM</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.keytab.location" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.caller.principal.name" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> </orawsp:PropertySet> </orawsp:Config> </orawsp:bindings> </orasp:wss11-sts-issued-token-with-certificates>
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service client.
This policy requires you to set up the Oracle WSM keystore to specify a key (username/password or X.509) to authenticate to the STS. See "Configuring Keystores for Message Protection".
See "Programmatic Configuration Overrides for WS-Trust Client Policies" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias, or override it on a per-client basis when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.enc.csf.key, or override them on a per-client basis when you attach the policy.
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service client.
This policy requires you to set up the Oracle WSM keystore to specify a key (username/password or X.509) to authenticate to the STS. See "Configuring Keystores for Message Protection".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override. See "Programmatic Configuration Overrides for WS-Trust Client Policies" for examples of overriding STS configuration settings.
Configure the policy assertion for message signing, message encryption, or both.
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias, or override it on a per-client basis when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.enc.csf.key, or override them on a per-client basis when you attach the policy.
This policy authenticates a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using WS-Security's Basic 128 suite of symmetric key technologies.
This policy contains the following assertion template: oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template. See "WS-Trust Assertion Templates" for more information about the assertion.
The oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy assertion is as follows:
<orasp:wss11-sts-issued-token-with-certificates xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy" xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" orasp:require-applies-to="true" orasp:require-client-entropy="true" orasp:require-server-entropy="true" orasp:trust-version="13" orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="security/authentication, security/msg-protection" orawsp:name="WS-Security 1.1, issued tokee"> <orasp:issued-token orasp:require-external-reference="true" orasp:require-internal-reference="true" orasp:use-derived-keys="false"> <orasp:request-security-token-template orasp:algorithm-suite="Basic128" orasp:key-type="Symmetric" orasp:token-type="SAML11"/> </orasp:issued-token> <orasp:x509-token orasp:enc-key-ref-mech="thumbprint" orasp:is-encrypted="false" orasp:is-signed="true" orasp:sign-key-ref-mech="thumbprint"/> <orasp:msg-security orasp:algorithm-suite="Basic128" orasp:confirm-signature="true" orasp:encrypt-signature="false" orasp:include-timestamp="true" orasp:sign-then-encrypt="true" orasp:use-derived-keys="false"> <orasp:request> <orasp:signed-parts> <orasp:body/> <orasp:header orasp:namespace="http://www.w3.org/2005/08/addressing"/> <orasp:header orasp:namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/> <orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/> </orasp:signed-parts> <orasp:encrypted-parts> <orasp:body/> <orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/> </orasp:encrypted-parts> </orasp:request> <orasp:response> <orasp:signed-parts> <orasp:body/> </orasp:signed-parts> <orasp:encrypted-parts> <orasp:body/> </orasp:encrypted-parts> </orasp:response> <orasp:fault/> </orasp:msg-security> <orawsp:bindings> <orawsp:Config orawsp:configType="declarative" orawsp:name="Wss11StsIssuedTokenWithCertsConfig"> <orawsp:PropertySet orawsp:name="standard-security-properties"> <orawsp:Property orawsp:contentType="optional" orawsp:name="keystore.enc.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="constant" orawsp:name="role" orawsp:type="string"> <orawsp:Value>ultimateReceiver</orawsp:Value> </orawsp:Property> </orawsp:PropertySet> </orawsp:Config> </orawsp:bindings> </orasp:wss11-sts-issued-token-with-certificates>
You can configure the properties shown in Table C-82. You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Attaching Web Service Policies Permitting Overrides".
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service.
This policy inserts a SAML sender vouches assertion issued by a trusted STS (Security Token Service). Messages are protected using the client's private key.
This policy contains the following assertion template: oracle/wss11_sts_issued_saml_with_message_protection_client_policy. See "WS-Trust Assertion Templates" for more information about the assertion.
The oracle/wss11_sts_issued_saml_with_message_protection_client_policy policy assertion is as follows:
<orasp:wss11-sts-issued-token-with-certificates xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy" xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" orasp:require-applies-to="true" orasp:require-client-entropy="true" orasp:require-server-entropy="true" orasp:trust-version="13" orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="security/authentication, security/msg-protection" orawsp:name="WS-Security 1.1, issued token"> <orasp:issued-token orasp:require-external-reference="true" orasp:require-internal-reference="true" orasp:use-derived-keys="false"> <orasp:request-security-token-template orasp:algorithm-suite="Basic128" orasp:token-type="SAML11"/> </orasp:issued-token> <orasp:x509-token orasp:enc-key-ref-mech="thumbprint" orasp:is-encrypted="false" orasp:is-signed="true" orasp:sign-key-ref-mech="direct"/> <orasp:msg-security orasp:algorithm-suite="Basic128" orasp:confirm-signature="true" orasp:encrypt-signature="false" orasp:include-timestamp="true" orasp:sign-then-encrypt="true" orasp:use-derived-keys="false"> <orasp:request> <orasp:signed-parts> <orasp:body/> <orasp:header orasp:namespace="http://www.w3.org/2005/08/addressing"/> <orasp:header orasp:namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/> <orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/> </orasp:signed-parts> <orasp:encrypted-parts> <orasp:body/> <orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/> </orasp:encrypted-parts> </orasp:request> <orasp:response> <orasp:signed-parts> <orasp:body/> </orasp:signed-parts> <orasp:encrypted-parts> <orasp:body/> </orasp:encrypted-parts> </orasp:response> <orasp:fault/> </orasp:msg-security> <orawsp:bindings> <orawsp:Config orawsp:configType="declarative" orawsp:name="Wss11StsIssuedTokenWithCertsConfig"> <orawsp:PropertySet orawsp:name="standard-security-properties"> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.user.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.x509.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:name="on.behalf.of" orawsp:type="boolean"> <orawsp:Value>true</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.on.behalf.of.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="keystore.recipient.alias" orawsp:type="string"> <orawsp:Value>orakey</orawsp:Value> </orawsp:Property> <orawsp:Property orawsp:contentType="optional" orawsp:name="keystore.enc.csf.key" orawsp:type="string"> <orawsp:Value/> </orawsp:Property> </orawsp:PropertySet> </orawsp:Config> </orawsp:bindings> </orasp:wss11-sts-issued-token-with-certificates>
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service client.
This policy requires you to set up the Oracle WSM keystore to specify a key (username/password or X.509) to authenticate to the STS. See "Configuring Keystores for Message Protection".
See "Programmatic Configuration Overrides for WS-Trust Client Policies" for a description of the configuration settings you can override.
Configure the policy assertion for message signing, message encryption, or both.
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias, or override it on a per-client basis when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.enc.csf.key, or override them on a per-client basis when you attach the policy.
See "Setting Up Automatic Policy Configuration: Main Steps" for information on how to set up the Web service client.
This policy requires you to set up the Oracle WSM keystore to specify a key (username/password or X.509) to authenticate to the STS. See "Configuring Keystores for Message Protection".
See "Using Client Programmatic Configuration Overrides" for a description of the configuration settings you can override. See "Programmatic Configuration Overrides for WS-Trust Client Policies" for examples of overriding STS configuration settings.
The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using Service Identity Certification Extension".
As an alternative, you can specify a value for keystore.recipient.alias, or override it on a per-client basis when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.
You can specify a value for keystore.enc.csf.key, or override them on a per-client basis when you attach the policy.
Configure the policy assertion for message signing, message encryption, or both.
This section describes the predefined MTOM policies.
There are two potential behaviors for using MTOM with Oracle Infrastructure Web services, depending on how you configure MTOM:
If you configure MTOM from Fusion Middleware Control by attaching the oracle/wsmtom_policy policy (either via local or Global Policy Attachment), the endpoint throws a fault if the request is not MTOM encoded. The MTOM policy rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format. In this use, requests must be MTOM-enabled.
If you configure MTOM for an ADF BC Web service outside of Fusion Middleware Control, such as by editing the MTOM-enabled switch in oracle-webservices.xml or by directly adding the @MTOM annotation to the Web service, the endpoint can accept MTOM requests but does not return a fault if the request is not MTOM encoded. In this use, requests might be MTOM-enabled, but there is no requirement that they must be.
SOAP Message Transmission Optimization Mechanism/XML-binary Optimized Packaging (MTOM/XOP) defines a method for optimizing the transmission of XML data of type xs:base64Binary or xs:hexBinary in SOAP messages.
The Message Transmission Optimization Mechanism (MTOM) policy rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format.
MTOM refers to specifications http://www.w3.org/TR/2005/REC-soap12-mtom-20050125 and http://www.w3.org/Submission/2006/SUBM-soap11mtom10-20060405 for SOAP 1.2 and SOAP 1.1 bindings, respectively.
To enable MTOM on the client of the Web service, pass the javax.xml.ws.soap.MTOMFeature as a parameter when creating the Web service proxy or dispatch, as illustrated in the following example.
package examples.webservices.mtom.client;
import javax.xml.ws.soap.MTOMFeature;
public class Main {
public static void main(String[] args) {
String FOO = "FOO";
MtomService service = new MtomService()
MtomPortType port = service.getMtomPortTypePort(new MTOMFeature());
String result = null;
result = port.echoBinaryAsString(FOO.getBytes());
System.out.println( "Got result: " + result );
}
}
WS-ReliableMessaging makes message exchanges reliable. It ensures that messages are delivered reliably between distributed applications regardless of software component, system, or network failures. Ordered delivery is assured and automatic retransmission of failed messages does not have to be coded by each client application.
Consider using reliable messaging if your Web service is experiencing the following problems:
network failures or dropped connections
messages are lost in transit
messages are arriving at their destination out of order
WS-ReliableMessaging considers the source and destination of a message to be independent of the client/server model. That is, the client and the server can each act simultaneously as both a message source and destination on the communications path.
This section describes the predefined Reliable Messaging policies.
Table 11-1 lists the properties that you can set for the WS-RM policies.
Table 11-1 WS-RM Policy Properties
| Property Name | Description | Default Value Used by Policy | Possible Values |
|---|---|---|---|
|
DeliveryAssurance |
Delivery assurance. The following defines the delivery assurance types:
|
InOrder |
InOrder AtLeastOnce AtLeastOnceInOrder ExactlyOnce ExactlyOnceInOrder AtMostOnce AtMostOnceInOrder |
|
StoreType |
Type of message store. |
InMemory |
InMemory FileSystem (not fully supported) JDBC |
|
StoreName |
Name of the message store. |
oracle |
String value |
|
jdbc-connection-name |
JNDI reference to a JDBC data source. This field is valid only if StoreType is set to JDBC. This value takes precedence over jdbc-connection-url. The username and password will be used if both are present. |
jdbc/MessagesStore |
Valid JDBC store |
|
InactivityTimeout |
Amount of time, in milliseconds, that can elapse between message exchanges associated with a particular WS-ReliableMessaging sequence. Once this value is reached, the sequence will be terminated and discarded automatically. |
600000 |
The amount of time in milliseconds. |
|
BaseRetransmissionInterval |
Interval, in milliseconds, that the source endpoint waits after transmitting a message and before it retransmits the message if it receives no acknowledgment for that message. |
3000 |
The amount of time in milliseconds. |
This policy provides support for version 1.0 of the Web Services Reliable Messaging protocol. This policy can be attached to any SOAP-based client or endpoint.
The Web service client will automatically detect the WSDL policy assertions at run time and use them to enable the advertised version of WS-RM on the client.
For multi-message sequences, the client code must include explicit invocations of methods for delimiting sequence boundaries. Otherwise, every message is wrapped in its own sequence
Edit the client to enable a reliable messaging session for the messages sent to the service. The oracle.webservices.rm.client.RMSessionLifecycle interface provides the client with a mechanism for demarcating WS-RM sequence boundaries.
Example 11-8 illustrates sample WS-RM client code. In the code, a new TestService is created. The TestPort, through which the client will communicate with the service, is retrieved. The port object is cast to a RMSessionLifecycle object and a reliable messaging session is opened on it (openSession). After the messages are sent to the service, the session is closed (closeSession).
Example 11-8 Sample WS-Rm Client Code
public class ClientServlet extends HttpServlet {
public void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
int num1 = Integer.parseInt(request.getParameter("num1"));
int num2 = Integer.parseInt(request.getParameter("num2"));
String outputStr = null;
TestService service = new TestService();
Test port = service.getTestPort();
try {
((RMSessionLifecycle) port).openSession();
outputStr = port.hello(inputStr);
} catch (Exception e) {
e.printStackTrace();
outputStr = e.getMessage();
} finally {
((RMSessionLifecycle) port).closeSession();
response.getOutputStream().write(outputStr.getBytes());
}
}
}
This policy provides support for version 1.1 of the Web Services Reliable Messaging protocol. This policy can be attached to any SOAP-based client or endpoint.
The Web service client will automatically detect the WSDL policy assertions at run time and use them to enable the advertised version of WS-RM on the client.
For multi-message sequences, the client code must include explicit invocations of methods for delimiting sequence boundaries. Otherwise, every message is wrapped in its own sequence
Edit the client to enable a reliable messaging session for the messages sent to the service. The oracle.webservices.rm.client.RMSessionLifecycle interface provides the client with a mechanism for demarcating WS-RM sequence boundaries.
Example 11-8 illustrates a servlet client. In the code, a new TestService is created. The TestPort, through which the client will communicate with the service, is retrieved. The port object is cast to a RMSessionLifecycle object and a reliable messaging session is opened on it (openSession). After the messages are sent to the service, the session is closed (closeSession).
This section describes the predefined Management policies.
This policy causes the request, response, and fault messages to be sent to a message log.
This policy contains the following assertion template: oracle/log_template. See "oracle/security_log_template" for more information about the assertion.
Determine whether you want to log messages for the request and response, based on the following categories:
all
header
SOAP body
SOAP envelope
Messages are logged to the message log for the domain.
To view the message log
In the navigator pane, expand WebLogic Domain to show the domain for which you want to see the logged messages. Select the domain.
Using Fusion Middleware Control, click WebLogic Domain, then Logs and then View Log Messages.
There are two ways to attach policies to Web service clients and Web services: at the client and service design time, and post deployment.
Post-deployment, you attach security and management policies to SOA composites, ADF, and WebCenter applications using the Oracle Enterprise Manager Fusion Middleware Control. This method provides the most power and flexibility because it moves Web service security to the control of the security administrator.
At design time, Oracle JDeveloper automates ADF and SOA client policy attachment. Or, you can attach Oracle WSM security and management policies to applications programmatically. You typically do this using your favorite IDE, such as Oracle JDeveloper.
Either way, the client-side policy must be the equivalent of the one associated with the Web service. If the two files are different, and there is a conflict in the assertions contained in the files, then the invoke of the Web service operation returns an error.
For example, if the oracle/wss_http_token_over_ssl_service_policy policy requires mutual authentication, the client policy must also be set for mutual authentication.
For the predefined policies, both client and Web service policies are included. If you create a new policy, generating the policy as described in "Creating Web Service Policies" increases the likelihood that the client policy will work with the service policy.
"Attaching Client Policies Permitting Overrides" describes the policy configuration override feature that allows you to specify certain Web service client configuration information when you attach a policy. However, you can also override this configuration information programmatically at design time. This section describes client programmatic overrides.
Table 11-2 shows the properties you can set via programmatic configuration overrides for a given policy. Example 11-9 shows an example of setting these properties from a program.
Table 11-2 Properties Set Via Programmatic Configuration Overrides
| Property List | Description | Applies to These Policies |
|---|---|---|
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.CALLER_PRINCIPAL_NAME |
Client's principal name as generated using the Note: |
wss11_kerberos_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_CSF_KEY |
Gets the username and password corresponding to the csf-key specified in the credential store if the credential store is available to the client. Instead of using this property, you can also explicitly set the username and password as shown in Example 11-9 |
oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss_username_token_client_policy oracle/wss_username_token_over_ssl_client_policy oracle/wss10_username_id_propagation_with_msg_protection_client_policy oracle/wss_http_token_client_policy oracle/wss_http_token_over_ssl_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_LOCATION |
This property sets the location of the keystore file. If provided, this value will override any statically configured value. Type: java.lang.String |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy oracle/wss11_kerberos_token_with_message_protection_client_policy oracle/wss11_message_protection_client_policy oracle/wss11_saml_token_with_message_protection_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss11_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_TYPE |
This property sets the type of keystore file. If provided, this value will override any statically configured value. Type: java.lang.String Default is JKS. |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy oracle/wss11_kerberos_token_with_message_protection_client_policy oracle/wss11_message_protection_client_policy oracle/wss11_saml_token_with_message_protection_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss11_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_PASSWORD |
This property sets the password of the keystore file. If provided, this value will override any statically configured value. Type: java.lang.String |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy oracle/wss11_kerberos_token_with_message_protection_client_policy oracle/wss11_message_protection_client_policy oracle/wss11_saml_token_with_message_protection_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss11_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_SIG_KEY_ALIAS |
This property sets the alias of the key within the keystore that will be used for digital signatures. If provided, this value will override any statically configured value. Type: java.lang.String For WSS11 policies, this property is used only in the case of mutual authentication. |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy oracle/wss11_kerberos_token_with_message_protection_client_policy oracle/wss11_message_protection_client_policy oracle/wss11_saml_token_with_message_protection_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss11_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_SIG_KEY_PASSWORD |
This property sets the password for the alias of the key within the keystore that will be used for digital signatures. If provided, this value will override any statically configured value. Type: java.lang.String For WSS11 policies, this property is used only in the case of mutual authentication. |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy oracle/wss11_kerberos_token_with_message_protection_client_policy oracle/wss11_message_protection_client_policy oracle/wss11_saml_token_with_message_protection_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss11_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_ENC_KEY_ALIAS |
This property sets the alias of the key within the keystore that will be used to decrypt the response from the service. If provided, this value will override any statically configured value. Type: java.lang.String Not used in WSS11 policies. |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_ENC_KEY_PASSWORD |
This property sets the password for the key within the keystore that will be used for decryption. If provided, this value will override any statically configured value. Type: java.lang.String Not used in WSS11 policies. |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_RECIPIENT_KEY_ALIAS |
This property sets the alias for the recipient's public key that is used to encrypt type outbound message. If provided this value will override any static configuration value. Type: java.lang.String |
oracle/wss10_message_protection_client_policy oracle/wss10_saml_hok_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_integrity_client_policy oracle/wss10_saml_token_with_message_protection_client_policy oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy oracle/wss10_username_token_with_message_protection_client_policy oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy oracle/wss10_x509_token_with_message_protection_client_policy oracle/wss11_kerberos_token_with_message_protection_client_policy oracle/wss11_message_protection_client_policy oracle/wss11_saml_token_with_message_protection_client_policy oracle/wss11_username_token_with_message_protection_client_policy oracle/wss11_x509_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_SUBJECT_PRECEDENCE |
In case of SAML client policies, set this property to false if there is a need to use a client-specified username rather than subject. |
Applies to all of the SAML client policies listed in "Configuring SAML". |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_SAML_ISSUER_NAME |
This property sets the SAML issuer name when trying access a service that is protected using SAML mechanism. If provided this value will override any static configuration value. Type: java.lang.String |
Applies to all of the SAML client policies listed in "Configuring SAML". |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_INCLUDE_USER_ROLES |
This property sets the user roles in a SAML assertion. |
Applies to all of the SAML client policies listed in "Configuring SAML". |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_SAML_ASSERTION_FILE_NAME |
For SAML HOK policies, this file contains the assertion |
Applies to all of the SAML client policies listed in "Configuring SAML". |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KERBEROS_SERVICE_PRINCIPAL |
This property sets the service principal name when trying access a service that is protected using the Kerberos mechanism. If provided this value will override any static configuration value. Type: java.lang.String |
oracle/wss11_kerberos_token_with_message_protection_client_policy |
|
BindingProvider.USERNAME_PROPERTY ( |
User name for authentication. |
Used by username policies, and SAML policies including identity switching policies. For username client policies, you have two options:
For SAML client policies including the identity switch policy, use |
|
BindingProvider.PASSWORD_PROPERTY ( |
Password for authentication. |
Used by username client policies. |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY |
Use to configure X509 certificate for authenticating to the STS. If the |
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY |
Use to configure the username/password to authenticate to the STS. If |
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_STS_AUTH_ON_BEHALF_OF_CSF_KEY |
Optional property. Use to configure on behalf of entity. If present, it will be given preference over Subject (if it exists). |
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.ON_BEHALF_OF |
Optional property. Override this property to indicate whether the request is on behalf of an another entity. The default value for this flag is true. When set to true and Otherwise, if the subject is already established, then the username from the subject will be sent as If |
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.STS_KEYSTORE_RECIPIENT_ALIAS |
The public key alias of the STS. |
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.ATTESTING_MAPPING_ATTRIBUTE |
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. |
wss10_saml20_token_with_message_protection_client_policy wss11_saml20_token_with_message_protection_client_policy |
|
oracle.wsm.security.util.SecurityConstants.ClientConstants.SAML_AUDIENCE_URI |
Represents the relying party, as a comma-separated URI. This field accepts wildcards. |
wss10_saml_token_client_policy wss10_saml20_token_client_policy wss_saml_token_bearer_over_ssl_client_policy wss_saml20_token_bearer_over_ssl_client_policy wss_saml_token_over_ssl_client_policy wss_saml20_token_over_ssl_client_policy wss10_saml_token_with_message_protection_client_policy wss10_saml20_token_with_message_protection_client_policy wss11_saml_token_with_message_protection_client_policy wss11_saml20_token_with_message_protection_client_policy |
Example 11-9 shows an example of a Web service client overriding the keystore and username/password.
If you need to clear an overridden configuration property, set it to an empty string.
Before you clear it, remember that other policies could be using the same property. The properties are client-specific and there could be multiple policies that are attached to the same client that use the same property.
Example 11-9 Overriding the Keystore and Username/Password
package example;
import oracle.wsm.security.utils.SecurityConstants;
public class MyClientJaxWs {
public static void main(String[] args) {
try {
URL serviceWsdl = new URL("http://localhost/myApp/myPort?WSDL");
QName serviceName = new QName("MyNamespace", "MyService");
Service service = Service.create(serviceWsdl, serviceName);
MyInterface proxy = service.getPort(MyInterface.class);
RequestContext context = ((BindingProvider)proxy).getRequestContext();
context.put(oracle.webservices.ClientConstants.CLIENT_CONFIG, new File( "c:/dat/client-pdd.xml" ) );
context.put(BindingProvider.USERNAME_PROPERTY, getCurrentUsername() );
context.put(BindingProvider.PASSWORD_PROPERTY, getCurrentPassword() );
context.put(SecurityConstants.ClientConstants.WSS_KEYSTORE_LOCATION, "c:/mykeystore.jks");
context.put(SecurityConstants.ClientConstants.WSS_KEYSTORE_PASSWORD, "keystorepassword" );
context.put(SecurityConstants.ClientConstants.WSS_KEYSTORE_TYPE, "JKS" );
context.put(SecurityConstants.ClientConstants.WSS_SIG_KEY_ALIAS, "your signature alias" );
context.put(SecurityConstants.ClientConstants.WSS_SIG_KEY_PASSWORD, "your signature password" );
context.put(SecurityConstants.ClientConstants.WSS_ENC_KEY_ALIAS, "your encryption alias" );
context.put(SecurityConstants.ClientConstants.WSS_ENC_KEY_PASSWORD, "your encryption password" );
System.out.println(proxy.myOperation("MyInput"));
} catch (Exception e) {
e.printStackTrace();
}
}
}
In Example 11-9, the contents of c:/dat/client-pdd.xml referenced might be as follows:
! -- The contents of c:/dat/client-pdd.xml file mentioned above -- >
<oracle-webservice-clients>
<webservice-client>
<port-info>
<policy-references>
<policy-reference uri="management/Log_Msg_Policy" category="management"/>
<policy-reference uri="oracle/wss10_username_token_with_message_protection_client_policy" category="security"/>
</policy-references>
</port-info>
</webservice-client>
</oracle-webservice-clients>
Oracle WSM supports a SOA local optimization feature for composite-to-composite invocations in which the reference of one composite specifies a Web service binding to a second composite running in the same container. Local optimization enables you to bypass the HTTP stack and SOAP/normalized message conversions during run time.
This SOA local optimization feature is described in "Policy Attachments and Local Optimization in Composite-to-Composite Invocations" in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite and summarized here.
There are two ways to control the local optimization feature, and they have different scope:
By adding the oracle.webservices.local.optimization property in the binding section of the composite.xml file. There are two possible values, true and false:
true -- Local optimization is used if the policy supports it as shown in Table 11-3 and the policy-level control is configured to use it as described in "Configuring the Policy-Level Optimization Control".
If optimization is used, the policy is not applied.
false -- Local optimization is not used, regardless of the how the policy-level control is configured and the default policy setting for the local-optimization property shown in Table 11-3.
This setting forces the policy to be applied.
The composite-level property is independent of the policy-level configuration. That is, if you want to turn off the optimization regardless of whether a policy is attached, set the composite-level property to false.
See "Policy Attachments and Local Optimization in Composite-to-Composite Invocations" for information on overriding the local-optimization setting for a policy by adding the oracle.webservices.local.optimization property in the binding section of the composite.xml file.
By configuring the optimization control for a policy, as described in "Configuring the Policy-Level Optimization Control". The policy-level property controls the optimization wherever the policy is used, except as overridden by the composite-level property.
Notes:
If there is a policy attached to the Web service, the policy may not be invoked if this optimization is used. Therefore, for each policy you need to decide whether you want to use the local optimization.Oracle recommends that you do not change the optimization settings for the predefined policies because doing so may cause the policies to not be invoked, resulting in unexpected behavior.
The optimization control is available when you create or edit a policy, as shown in Figure 11-4.
Figure 11-4 Local Optimization Control When Creating a Policy
There are three possible settings for the Local Optimization control: On, Off, and Check Identity:
On -- Optimization is turned on and the policy is not applied.
Off -- Optimization is turned off and the policy is applied. The request goes through the usual WS/SOAP/HTTP process.
Check Identity -- Optimize only if a JAAS subject already exists in the current thread, indicating that authentication has already succeeded. Otherwise, go through the usual WS/SOAP/HTTP process.
Table 11-3 shows the predefined policies, and describes how each policy implements the local optimization feature.
Table 11-3 Default Optimization Setting of Predefined Policies
| Policy Name | Default Optimization Setting |
|---|---|
|
oracle/wsaddr10_policy |
On |
|
oracle/binding_authorization_denyall_policy |
Always Off |
|
oracle/binding_authorization_permitall_policy |
Always Off |
|
oracle/binding_permission_authorization_policy |
Always Off |
|
oracle/component_authorization_all_policy |
Does not apply to bindings |
|
oracle/log_policy |
On |
|
oracle/no_addressing_policy |
Off |
|
oracle/no_authentication_client_policy |
Off |
|
oracle/no_authentication_service_policy |
Off |
|
oracle/no_authorization_component_policy |
Off |
|
oracle/no_authorization_service_policy |
Off |
|
oracle/no_messageprotection_client_policy |
Off |
|
oracle/no_messageprotection_service_policy |
Off |
|
oracle/no_mtom_policy |
Off |
|
oracle/no_wsrm_policy |
Off |
|
oracle/sts_trust_config_client_policy |
Off |
|
oracle/sts_trust_config_service_policy |
Off |
|
oracle/whitelist_authorization_policy |
Always Off |
|
oracle/wsaddr_policy |
On |
|
oracle/wsmtom_policy |
On |
|
oracle/wsrm10_policy |
On |
|
oracle/wsrm11_policy |
On |
|
oracle/wss_http_token_client_policy |
Off |
|
oracle/wss_http_token_service_policy |
Off |
|
oracle/wss_http_token_over_ssl_client_policy |
Off |
|
oracle/wss_http_token_over_ssl_service_policy |
Off |
|
oracle/wss11_kerberos_token_client_policy |
Off |
|
oracle/wss11_kerberos_token_service_policy |
Off |
|
oracle/wss_username_token_client_policy |
Off |
|
oracle/wss_username_token_service_policy |
Off |
|
oracle/wss_username_token_over_ssl_client_policy |
Off |
|
oracle/wss_username_token_over_ssl_service_policy |
Off |
|
oracle/wss10_message_protection_client_policy |
On |
|
oracle/wss10_message_protection_service_policy |
On |
|
oracle/wss10_username_token_with_message_protection_client_policy |
Off |
|
oracle/wss10_username_token_with_message_protection_service_policy |
Off |
|
oracle/wss10_x509_token_with_message_protection_client_policy |
Off |
|
oracle/wss10_x509_token_with_message_protection_service_policy |
Off |
|
oracle/wss10_saml_token_with_message_protection_client_policy |
Check Identity |
|
oracle/wss10_saml_token_with_message_protection_service_policy |
Check Identity |
|
oracle/wss11_saml_token_with_message_protection_client_policy |
Check Identity |
|
oracle/wss11_saml_token_with_message_protection_service_policy |
Check Identity |
|
oracle/wss11_saml20_token_with_message_protection_client_policy |
Check Identity |
|
oracle/wss11_saml20_token_with_message_protection_service_policy |
Check Identity |
|
oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy |
Off |
|
oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy |
Off |
|
oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
Off |
|
oracle/wss11_sts_issued_saml_with_message_protection_client_policy |
Off |
|
oracle/wss10_saml_token_with_message_integrity_client_policy |
Check Identity |
|
oracle/wss10_saml_token_with_message_integrity_service_policy |
Check Identity |
|
oracle/wss10_saml20_token_with_message_protection_client_policy |
Check Identity |
|
oracle/wss10_saml20_token_with_message_protection_service_policy |
Check Identity |
|
oracle/wss10_saml_token_client_policy |
Check Identity |
|
oracle/wss10_saml_token_service_policy |
Check Identity |
|
oracle/wss10_saml20_token_client_policy |
Check Identity |
|
oracle/wss10_saml20_token_service_policy |
Check Identity |
|
oracle/wss10_username_id_propagation_with_msg_protection_client_policy |
Check Identity |
|
oracle/wss10_username_id_propagation_with_msg_protection_service_policy |
Check Identity |
|
oracle/wss11_message_protection_client_policy |
On |
|
oracle/wss11_message_protection_service_policy |
On |
|
oracle/wss11_username_token_with_message_protection_client_policy |
Off |
|
oracle/wss11_username_token_with_message_protection_service_policy |
Off |
|
oracle/wss11_x509_token_with_message_protection_client_policy |
Off |
|
oracle/wss11_x509_token_with_message_protection_service_policy |
Off |
|
oracle/wsrm10_policy |
On |
|
oracle/wsrm11_policy |
On |
|
oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy |
Off |
|
oracle/wss10_username_token_with_message_protection_ski_basic256_service_policy |
Off |
|
oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy |
Check Identity |
|
oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy |
Check Identity |
|
wss11_saml_or_username_token_with_message_protection_client_policy |
Check Identity |
|
wss11_saml_or_username_token_with_message_protection_service_policy |
Check Identity |
|
wss11_saml_token_identity_switch_with_message_protection_client_policy |
Off |
|
wss10_saml_hok_token_with_message_protection_client_policy |
Off |
|
wss10_saml_hok_token_with_message_protection_service_policy |
Off |
|
oracle/wss_saml_or_username_token_over_ssl_service_policy |
Check Identity |
|
oracle/wss_saml_or_username_token_service_policy |
Check Identity |
|
wss_saml_token_over_ssl_client_policy |
Check Identity |
|
wss_saml_token_over_ssl_service_policy |
Check Identity |
|
wss_saml20_token_over_ssl_client_policy |
Check Identity |
|
wss_saml20_token_over_ssl_service_policy |
Check Identity |
|
wss_saml_token_bearer_over_ssl_client_policy |
Check Identity |
|
wss_saml_token_bearer_over_ssl_service_policy |
Check Identity |
|
oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy |
Off |
|
oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy |
Off |
|
wss_saml20_token_bearer_over_ssl_client_policy |
Check Identity |
|
wss_saml20_token_bearer_over_ssl_service_policy |
Check Identity |
|
wss11_kerberos_token_with_message_protection_client_policy |
Off |
|
wss11_kerberos_token_with_message_protection_service_policy |
Off |
|
wss11_kerberos_token_with_message_protection_basic128_client_policy |
Off |
|
wss11_kerberos_token_with_message_protection_basic128_service_policy |
Off |
|
 Copyright © 2007, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|