Knowledge of the format of these map constructs is often not required in order to set them. For example when you configure the properties using OpenSSO Enterprise Console, you do not interact with the “<key>[<name>]=<value>” formatting involved with map constructs. However, if you use OpenSSO Enterprise Console to set a map, though the formatting information provided in this section is not applicable, the general information about maps is useful.
See the following table to determine when the map construct format is required to set this property.
Table 4–2 Use of the Map Construct Format: Required or Not
Method for Setting Properties |
Location of Agent Configuration |
Use of Map Construct Format Required |
Using the OpenSSO Enterprise Console |
Centralized agent configuration |
NO |
Using the ssoadm command-line utility |
Centralized agent configuration |
YES |
Using the OpenSSOAgentConfiguration.properties file |
Local agent configuration |
YES |
Certain J2EE agent properties are specified as maps. A map construct has the following format (Does not apply when OpenSSO Enterprise Console is used):
<key>[<name>]=<value>
The configuration key (name of the configuration property)
A string that forms the lookup key as available in the map
The value associated with the name in the map
Properties that are specified in this manner must follow the preceding format, otherwise they will be treated as invalid or missing properties.
For a given <name>, there may only be one entry in the configuration for a given configuration key (<key>). If multiple entries with the same <name> for a given configuration key are present, only one of the values will be loaded in the system and the other values will be discarded.
com.sun.identity.agents.config.filter.mode[app1]=ALL com.sun.identity.agents.config.filter.mode[app2]=SSO_ONLY