Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-933

In-memory tokens expire after 5 minutes of inactivity

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.0.1
    • 1.3
    • Caching
    • None

      The in-memory cache used by Crowd for session tokens expires those tokens after 5 minutes of inactivity, ignoring the session timeout specified in the Crowd Console. To adjust the time-out, you need to alter the file used to configure the cache and restart Crowd.

      For Crowd versions prior to 1.4, please add the following entry to the <CROWD>/crowd-webapp/WEB-INF/classes/crowd-ehcache.xml file:

      <cache name="com.atlassian.crowd.model.token.Token"
        maxElementsInMemory="50000"
        eternal="true"
        overflowToDisk="false"
        diskPersistent="false"/>

      Crowd versions 1.4 to 1.6 need modification of an existing entry in the <CROWD>/crowd-webapp/WEB-INF/classes/crowd-ehcache.xml file. Change eternal to true in the entry below:

      <defaultCache
        maxElementsInMemory="10000"
        eternal="true"
        overflowToDisk="false"
        timeToIdleSeconds="300"
        timeToLiveSeconds="300"
        diskPersistent="false"
        diskExpiryThreadIntervalSeconds="120"/>

      For Crowd 2.0 the following 2 caches need to be added to the crowd-ehcache.xml

      <cache name="com.atlassian.crowd.model.token.Token.random-hash-cache"
        maxElementsInMemory="10000"
        eternal="true"
        overflowToDisk="false"
        diskPersistent="false"
        />

<cache name="com.atlassian.crowd.model.token.Token.identifier-hash-cache"
        maxElementsInMemory="10000"
        eternal="true"
        overflowToDisk="false"
        diskPersistent="false"
        />

      For more technical readers: This means that Crowd's internal cache will hold onto the tokens until our token-expiration process removes them, at the time specified in the Crowd Console. Prior to this, the cache would remove the tokens after its default timeout of five minutes.

            [CWD-933] In-memory tokens expire after 5 minutes of inactivity

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1509895 ] New: JAC Bug Workflow v3 [ 3364824 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392404 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1509895 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273419 ] New: Simplified Crowd Development Workflow v2 [ 1392404 ]
            jawong.adm made changes -
            Workflow Original: JIRA Bug Workflow v2 [ 174458 ] New: Crowd Development Workflow v2 [ 273419 ]
            Justin Koke made changes -
            Assignee Original: David O'Flynn [Atlassian] [ doflynn ] New: Justin Koke [ justin@atlassian.com ]
            Resolution New: Fixed [ 1 ]
            Status Original: Verified [ 10005 ] New: Resolved [ 5 ]
            Justin Koke made changes -
            Status Original: Open [ 1 ] New: Verified [ 10005 ]
            Justin Koke made changes -
            Description Original: The in-memory cache used by Crowd for session tokens expires those tokens after 5 minutes of inactivity, ignoring the session timeout specified in the Crowd Console. To adjust the time-out, you need to alter the file used to configure the cache and restart Crowd.
             
            For Crowd versions *prior to 1.4*, please add the following entry to the {{<CROWD>/crowd-webapp/WEB-INF/classes/crowd-ehcache.xml}} file:
            {code}
            <cache name="com.atlassian.crowd.model.token.Token"
                    maxElementsInMemory="50000"
                    eternal="true"
                    overflowToDisk="false"
                    diskPersistent="false"/>
            {code}

            Crowd versions *1.4 and later* need modification of an existing entry in the {{<CROWD>/crowd-webapp/WEB-INF/classes/crowd-ehcache.xml}} file. Change eternal to {{true}} in the entry below:
            {code}
            <defaultCache
                    maxElementsInMemory="10000"
                    eternal="true"
                    overflowToDisk="false"
                    timeToIdleSeconds="300"
                    timeToLiveSeconds="300"
                    diskPersistent="false"
                    diskExpiryThreadIntervalSeconds="120"/>
            {code}

            For more technical readers: This means that Crowd's internal cache will hold onto the tokens until our token-expiration process removes them, at the time specified in the Crowd Console. Prior to this, the cache would remove the tokens after its default timeout of five minutes.             		New: The in-memory cache used by Crowd for session tokens expires those tokens after 5 minutes of inactivity, ignoring the session timeout specified in the Crowd Console. To adjust the time-out, you need to alter the file used to configure the cache and restart Crowd.
             
            For Crowd versions *prior to 1.4*, please add the following entry to the {{<CROWD>/crowd-webapp/WEB-INF/classes/crowd-ehcache.xml}} file:
            {code}
            <cache name="com.atlassian.crowd.model.token.Token"
                    maxElementsInMemory="50000"
                    eternal="true"
                    overflowToDisk="false"
                    diskPersistent="false"/>
            {code}

            Crowd versions *1.4 to 1.6* need modification of an existing entry in the {{<CROWD>/crowd-webapp/WEB-INF/classes/crowd-ehcache.xml}} file. Change eternal to {{true}} in the entry below:
            {code}
            <defaultCache
                    maxElementsInMemory="10000"
                    eternal="true"
                    overflowToDisk="false"
                    timeToIdleSeconds="300"
                    timeToLiveSeconds="300"
                    diskPersistent="false"
                    diskExpiryThreadIntervalSeconds="120"/>
            {code}

            For Crowd 2.0 the following *2* caches need to be added to the {{crowd-ehcache.xml}}
            {code:xml}
            <cache name="com.atlassian.crowd.model.token.Token.random-hash-cache"
                    maxElementsInMemory="10000"
                    eternal="true"
                    overflowToDisk="false"
                    diskPersistent="false"
                    />

            <cache name="com.atlassian.crowd.model.token.Token.identifier-hash-cache"
                    maxElementsInMemory="10000"
                    eternal="true"
                    overflowToDisk="false"
                    diskPersistent="false"
                    />
            {code}

            For more technical readers: This means that Crowd's internal cache will hold onto the tokens until our token-expiration process removes them, at the time specified in the Crowd Console. Prior to this, the cache would remove the tokens after its default timeout of five minutes.
            shihab made changes -
            Fix Version/s New: 2.0.1 [ 14670 ]
            Support Count Updater made changes -
            Support reference count New: 5
            Justin Koke made changes -
            Workflow Original: jira [ 124015 ] New: JIRA Bug Workflow v2 [ 174458 ]

              justin@atlassian.com Justin Koke
              doflynn David O'Flynn [Atlassian]
              Affected customers:
              4 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: