The time after which the SecurityInfo strings that HPE Community Component generates as part of a secure query expire, unless they are refreshed. You can set SecurityTokenRefreshInterval to determine when to refresh the token.

If you enable token refreshing, you can set SecurityTokenLifetime to the total lifetime of the token (that is, you cannot refresh the token after this amount of time has elapsed, even if the current token is within the SecurityTokenIdleTime).

By default, SecurityTokenIdleTime is set to zero (disabled), and HPE Community Component uses only the SecurityTokenLifetime to determine when to expire a token. When you set SecurityTokenIdleTime, the default value of SecurityTokenLifetime increases to 12hours.


You must set SecurityTokenIdleTime to a value less than the value of SecurityTokenLifetime to enable token refreshing.

If you set SecurityTokenIdleTime to be larger than SecurityTokenLifetime, the default of SecurityTokenLifetime increases to 12hours, but the token expires before it refreshes.

Specify an interval in the following format:




is the number of time units to elapse.


is the time unit to apply. The following units are available:

  • second
  • seconds
  • minute
  • minutes
  • hour
  • hours
  • day
  • days
  • week
  • weeks
  • month
  • months
  • year

If you do not specify a TimeUnit, HPE Community Component reads the specified number as seconds.


The times used in the SecurityInfo strings are in Universal Coordinate Time (UTC or GMT) rather than local time.

Type: Long
Default: 0
Allowed Range: Minimum: 0
Maximum: 1year
Recommended Range: Minimum: 60seconds
Maximum: value of SecurityTokenLifetime
Required: No
Configuration Section: Security
Example: SecurityTokenIdletime=30minutes
See Also: