Before you implement SAML token (sender vouches) with message protection for interoperability between an OWSM 14c web service and a GlassFish client, you must complete a number of high-level tasks.

To configure prerequisites for interoperability:

1. Create a default-keystore.jks file with the following command:

   $JAVA_HOME/bin/keytool -genkeypair -alias orakey -keypass password -keyalg RSA
    -dname "CN=orakey, O=oracle C=us" -keystore default-keystore.jks -storepass
    password

2. Copy default-keystore.jks to the domain's fmwconfig directory.

3. Create a file user in GlassFish with the following command:

   $<GLASSFISHV3_HOME>/glassfish/bin/asadmin create-file-user

   For more information, see http://download.oracle.com/docs/cd/E18930_01/html/821-2433/create-file-user-1.html.

4. Add the user. For more information, see "Create users" in Oracle WebLogic Server Administration Console Online Help.

5. Import orakey from default-keystore.jks into GlassFish keystore and truststore. These are located in the directory <domain-dir>/config.

   $JAVA_HOME/bin/keytool -importkeystore -srckeystore
    <path-to>/default-keystore.jks -destkeystore
    <path-to-gf-domain>/config/cacerts.jks -srcalias  orakey -destalias orakey
    -srckeypass password -destkeypass changeit

6. Copy jps-config.xml and default-keystore.jks from the domain's fmwconfig directory into a local folder.

You can create an OWSM 11g web service and attach the SAML token with message protection service policy to achieve interoperability with a GlassFish client.

To configure an OWSM 11g web service:

1. Create a web service.

2. Attach the following policy to the web service:

   oracle/wss11_saml_token_with_message_protection_service_policy

   For more information, see "Attaching Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

You can configure a GlassFish client to implement SAML token with message protection for interoperability with an OWSM 11g web service.

To configure a GlassFish/Metro client:

1. Using NetBeans, create a Metro client by selecting New Project > Java > Java Application. Provide a project name and location. Select the server to deploy and select Finish.

2. Right-click the project. Select New > Web Service Client. Follow the wizard and provide WSDL URL for service deployed in WebLogic.

3. Create a SAML CallbackHandler that can be used with WSIT SAML Security Mechanisms supported by NetBeans.

   1. Place the file in the source folder of the project.

   2. Ensure issuer variable value is the same as in the jps-config.xml file created in Step 5 of Configuring Prerequisites for Interoperability for GlassFish Client.

   3. Set the urn reference to urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.

   4. Set the user created in Step 3 and Step 4 of Configuring Prerequisites for Interoperability for GlassFish Client. For example, to set the user to wlsuser, modify the file as follows: CN=wlsuser,OU=SU,O=wlsuser,L=Los Angeles,ST=CA,C=US.

4. To configure the JVM, log on to the GlassFish Administration Console.

   1. In the left pane, expand Configuration and click JVM Setting.

   2. In the right pane, click JVM Option tab.

   3. Click Add JVM Option. A new text field is displayed. Enter -DWSIT_HOME=${com.sun.aas.installRoot}.

   4. Click Enterprise Server in left pane.

   5. Click Restart in the right pane to restart the server.

   For more information, see Oracle GlassFish Server 3.1 Administration Guide at: http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gepzd.html.

5. Expand Web Services Reference node. Using NetBeans, right click Service Reference and select Edit Web Services Attributes.

6. For SAML Callback Handler option, click Browse and select the file from Step 3.

7. Set the alias in Keystore and Truststore.

8. Open index.jsp file. Right click and select Web Service Client Reference. Select Operation in Select Operation to Invoke dialog box and click ok.

9. Run the project.

Before you implement SAML token (sender vouches) with message protection for interoperability between a GlassFish web service and an OWSM 14c client, you must complete a number of high-level tasks.

To configure prerequisites for interoperability:

1. Create a default-keystore.jks file with the following command:

   $JAVA_HOME/bin/keytool -genkeypair -alias orakey -keypass password -keyalg RSA
    -dname "CN=orakey, O=oracle C=us" -keystore default-keystore.jks -storepass
    password

2. Copy default-keystore.jks to the domain's fmwconfig directory.

3. Save the credentials in credential store using WLST commands.

   For example:

   $<ORACLE_HOME>/common/bin/wlst.sh
   > connect()
   > createCred(map="oracle.wsm.security", key="keystore-csf-key",
    user="keystore", password="password")
   > createCred(map="oracle.wsm.security", key="sign-csf-key", user="orakey",
    password="password")
   > createCred(map="oracle.wsm.security", key="enc-csf-key", user="orakey",
    password="password")
   >createCred(map="oracle.wsm.security", key="glassfish.credentials" ,
    user="wlsUser" , password="password" , description="Glassfish user
    credentials");

   A cwallet.sso file is created in the directory DOMAIN_HOME/config/fmwconfig.

4. Create a file user in GlassFish with the following command:

   $<GLASSFISHV3_HOME>/glassfish/bin/asadmin create-file-user

   For more information, see http://download.oracle.com/docs/cd/E18930_01/html/821-2433/create-file-user-1.html.

5. Import orakey from default-keystore.jks into GlassFish keystore and truststore. These are located in the directory <domain-dir>/config.

   $JAVA_HOME/bin/keytool -importkeystore -srckeystore
    <path-to>/default-keystore.jks -destkeystore
    <path-to-gf-domain>/config/keystore.jks -srcalias  orakey -destalias orakey
    -srckeypass password -destkeypass changeit

6. Copy cwallet.sso, jps-config.xml and default-keystore.jks from the domain's fmwconfig directory into a local folder.

You can create a GlassFish web service and attach the SAML token with message protection service policy to achieve interoperability with an OWSM 11g client.

To configure a GlassFish/Metro web service:

1. Create a Metro web service.

   For more information, see https://javaee.github.io/metro/.

2. Configure the appropriate security mechanism. For more information, see https://javaee.github.io/metro/.

You can configure an OWSM 11g client to implement SAML token (sender vouches) with message protection for interoperability with a GlassFish web service.

To configure the OWSM 11g client:

1. Using JDeveloper, create a web service proxy for the GlassFish service. Select the policy oracle/wss11_saml_token_with_message_protection_client_policy in the wizard.

   For more information, see “Developing and Securing Web Services” in Developing Applications with Oracle JDeveloper.

2. Set the path to jps-config.xml created in Step 6 of “Configuring Prerequisites for Interoperability for GlassFish Web Service”.

3. Set the USERNAME_PROPERTY as follows: ((BindingProvider) sAMLTokenEchoService).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "wlsUser");

4. Invoke the web service.