Use this page to configure the Web Services Secure Conversation (WS-SecureConversation) client settings using the administrative console. The secure conversation client cache stores tokens on the client.
To view this administrative console page, click Services > Secure conversation client cache.
Sets the time that the token remains in cache after the token times out.
This field specifies the number of minutes for the time the token is in cache after the token expiration time expires (cache persist period). For example, if you specify 30 minutes, the token is kept in cache for this time period after the token expiration time. The default value is 10 minutes, which is the minimum number of minutes that is allowed.
Data type: | Integer |
Default: | 10 (minutes) |
Sets the time period before expiration that the client attempts to renew the token.
This field specifies the period of time, in minutes, before expiration that the client attempts to renew the token. This setting must specify a period of time that is longer than the time for the longest transaction or else the token might expire during the transaction. This time must include time for transport to and from the server, processing by the server, and any time delay that is because of time used for reliable messaging, when applicable. The default value is 10 minutes, which is the minimum number of minutes that is allowed.
If the Security Context Token
is renewed too often, it might cause Web Services Secure Conversation (WS-SecureConversation)
to fail or even cause an out-of-memory error to occur. It is recommended that
you set the renewal interval before the token expires value for the Secure
conversation client cache to a value less than the token timeout value for
the Security Context Token. It is also suggested that the token timeout value
be at least two times the renewal interval before the token expires value.
Data type: | Integer |
Default: | 10 (minutes) |
Specifies to enable or disable the use of a distributed cache.
Use this check box to specify whether to use distributed cache when the server is in a clustered environment and when the tokens are shared across the cluster.
Data type: | Check box |
Default: | No distributed cache (unchecked |
Specifies additional configuration settings that the secure conversation client might require.
This table lists custom properties. Use custom properties to set internal system configuration properties. This collection is empty until the first custom property is defined.
Data type: | String |
Specifies that you want to select further actions.
Use this check box to select custom properties for further actions. To manage existing custom properties, select the check box beside the name, and then select one of the following actions:
Actions | Description |
---|---|
Edit | Select to modify an existing custom property. This action is not displayed until you have added at least one custom property. |
Delete | Select to remove an existing custom property. |
Data type: | Check box |
Specifies that you want to add and define a new custom property.
Click New to define a new custom property.
Data type: | Button |
Lists available custom properties.
This column displays the names of the custom properties that you can use with the secure conversation client (for example, exampleProperty). Custom properties are name-value pairs of data, where the name is a string representation of a property that is expected by the secure conversation client.
Data type: | String |
Lists the values of the custom properties.
This column displays the values of the custom properties (for example, true). Custom properties are name-value pairs of data, where the value is a string representation of the property setting.
Data type: | String |