Federation Security Services Guide › Setup the SAML 1.x Assertion Generator File › SAML 1.x Assertion Generator Properties File › Configure the SAML 1.x AMAssertionGenerator.properties File

Configure the SAML 1.x AMAssertionGenerator.properties File

To configure the AMAssertionGenerator.properties file

1. Go to the following location: policy_server_home/config/properties.
2. Open the AMAssertionGenerator.properties file in a text editor.
3. Modify the following parameters:

   AssertionIssuerID

   Specifies the URL that identifies the site issuing the assertion.

   This URL must be the same value as the Issuer field that you complete for a SAML authentication scheme.

   Note: Set this value properly so that SAML 1.x assertions are meaningful.

   SecurityDomain

   Identifies the domain of the producer, such as example.com

   SourceID

   Specifies for the SAML 1.x artifact profile only, a unique ID in the artifact that identifies the producer. For more information, see the SAML specification at the OASIS website.

The values you enter in this file must match the values for the equivalent settings at the consumer site. The settings must match whether the consumer is a SAML Affiliate Agent or a 1.x consumer.

Note: If you update the AmAssertionGenerator.properties file, the Policy Server does not pick the changes until it is restarted.

Review the JVMOptions File Which Creates a JVM

The JVMOptions.txt File

The JVMOptions.txt file contains the settings that the Policy Server uses when creating the Java virtual machine that is used to support Federation Web Services. SAML 1.x, SAML 2.0, and WS‑Federation use this file.

During a Policy Server upgrade, the existing JVMOptions.txt file is renamed to JVMOptions.txt.backup. A new JVMOptions.txt file is created.

If the original file included customized parameters, be sure to modify the newly created file to include these customized parameters.

The installed location of this file is:

policy_server_home/config/

Important! If you update the JVMOptions.txt file, restart the Policy Server for the changes to take effect.

Notes:

• In some environments, logging off a system while the Policy Server is running causes the Policy Server service to fail. The failure is the result of a JVM issue. To prevent the failure, add the -Xrs command to its own command line in the JVMOptions.txt file. This java command reduces usage of operating system signals by the Java virtual machine.

  This command is case-sensitive so be sure to capitalize the X.

• If you encounter errors relating to missing classes, modify the classpath directive in this file. For complete information about the settings contained in the JVMOptions.txt file, see your Java documentation. The Java compiler directive java.endorsed.dirs is used in the JVMOptions.txt file to control class loading.